(Best read while listening to AEnima by Tool, loudly)

Dear Current Workplace,

Fuck you, for the reasons enumerated below.

Fuck your enterprise grey blue offices, the stifling warm air of a hundreds of bodies and sub par "development laptops".

Fuck your shitty carbonated water machines which were a cost saving measure over decent drinkable water.

Fuck your fake "flexi time", "you can do home office whenever you want" bullshit. You're still inviting me to mandatory meetings at 09:00 regularly.

Fuck your shitty, in house, third part IT provider sister company. They're the worst of all worlds. If it was in company, we'd get to give out to them, if it was an external company we'd fire them. And yes, when I quit I will quote the dumpster fire that is our corporate VPN as a major factor.

Fuck your cheery, bland, enterprise communication. Words coming under the corporate letterhead seem to lose all association with meaning. Agile, communication, open are things you write and profess to respect, but it seems your totally lack understanding of their meaning.

Fuck your client driven development. Sometime you actually have to fix the foundations before you can actually add new features. And fuck you management who keep on asking "why are there so many bugs and why is it always taking longer to deliver new releases". Because of you, you fucknuts, Because you can't say "NO" to the customer. Because you never listen to your own experienced developers.

Fuck your bullshit "code quality is important to us" line. If it's so important, then let us fix the heap of shit you're selling so that it works like a quasi functional program.

Fuck you development environment which has 250 projects in a single VS solution. Which takes 5mins plus to compile on a quad core i7 with 32 gb of ram.

Fuck this bullshit ball of mud "architecture". I spend most of my time trying to figure out where the logic should go and the rest of the time writing converters between different components. All because 7 years ago some idiot "architect" made a decision that they didn't have to live with.

Actually, fuck that guy in particular. Yeah, that guy who was the responsible architect for the project for 4 years and not once opened the solution to look a the code.

Fuck the manual testing of every business process. Manual setup of the entities takes 10mins plus and then when you run, boom either no message or some bullshit error code.

Fuck the antiquated technology choices which cause loads of bugs and slow down development. Fuck you for forcing me to do manual tests of another developers code at 20:00 on a Friday night because we can't get our act together to do this automatically.

Fuck you for making sure it's very clear I'm never going to be anything but a code monkey in this structure. Managers are brought in from outside.

Fuck you for being surprised that it's hard to hire competent developers in this second rate, overpriced town. It's hard to hire anywhere but this bland shithole would have anyone with half a clue running away at top speed.

Fuck you for valuing long hours and loyalty over actual performance. That one guy who everyone hated and was totally incompetent couldn't even get himself fired. He had to quit.

Fuck you for your mediocrity.

Fuck you for being the only employer for my skill-set in the region; paying just well enough that changing jobs locally doesn't make sense, but badly enough that it's difficult to move.

Fuck you for being the stable "safe" option so that any move is "risky".

Fuck your mediocrity.

Fuck you for being something I think about when I'm not at work. Not only is it shit from 9 to 5 you manage to suck the joy out of everything else in my life as well?

Fuck you for making me feel like a worse developer every day I work here. Fuck you for making every day feel like a personal and professional failure. Fuck you for making me seriously leave a career I love for something, anything else.

Fuck you for making the most I can hope for when I get up in the morning is to just make it until the night.

Yknow, I want to make an android app that I have in my mind for about half a year now and I already tried twice, both with Kotlin and with Java but everytime I try it's just pain and suffering and frustration...

No it's not because of the language, I like Java and I like Kotlin too and I'd say I'm at least decent at Kotlin and really good in Java...

No no.. the issue is the fucking Android SDK and the mix-and-match documentation available online!!!

Every fucking time I want to implement some sort of UI element, user action or a background service and I start googling how to do it It comes with with at least 3 different stack overflow solutions, all of them saying "that way of doing it is deprecated, instead you should X" and looking up the OFFICIAL FUCKING DOCS it will just make me roll up in the corner and cry because of how fucking inconsistent it is and the retarded domain language it uses... fucking transactions for fucking fragments inside fucking activities... because I guess the word "screen"/"view"/"template" or something similar natural just was too mainstream for the all knowing alphabet soup that google is...

And then you start looking up what the fucking difference even is and how to code it up only to find out there's at least 12 other opinions on how fragments should be used and what should be an activity and what should be a damn fragment...

But that's not all, that's just the base... I get a headache even thinking about how the fucking inflating of templates and the entire R. notation works. You want to open a fucking tiny corner menu with the settings options? WELL THEN YOU FUCKING BETTER REMEMBER TO IMPLEMENT IT THROUGH SOME SORT OF EVENT AND INFLATE THE MENU YOURSELF EVEN THOUGH ITS THE SAME FUCKING THING WITH STATIC STRINGS...

AND WHY THE FUCK DO I NEED LIKE 4 NEW FILES TO IMPLEMENT A FUCKING LISTVIEW...
also talking about ListViews... what was wrong with "ListView"... Why do we need a "RecyclerView"... oh right... because the fucks fucked the fuck up and all the legacy components were designed by a monkey and are next to useless! SO WE NEEDED A NEW NAME FOR THE FIXED VERSION, CANT NAME IT LISTVIEW AGAIN... FUCK YOU...

honestly... if I got a dolar for every "what the fuck android" I said during trying to understand that mess I'd be richer by a few hundred...

oh oh oh, but you know what? You don't like the android SDK? that's fine, you can use fucking React or Flutter or something... yeah.. because instead of torturing myself with the android SDK I want to torture myself with an abstraction of the same SDK and JavaScript as the fucking cherry on top... HAVE YOU FUCKING SEEN THE CODE FLUTTER SHOWS ON THEIR WEBSITE AS THE "Introduction" ?!!!

Look at this piece of shit:

[code in attached image, we could really use a proper Markdown support at least for rants]

THAT'S NOT EVEN THE ENTIRE THING, THAT'S JUST THE *REALLY* UGLY PART...

The fucking nesting... What is it with JS and all the fucking nesting everytime?! It looks like shit.... It reads like shit as well...

WHY, in the name OF FUCK, IS THERE MORE THAN 5 ANDROID FRAMEWORKS and ALL of them... used this FUCKING NOVEL idea of programming using A FUCKING BRACKET WALL

It always looks like:
(code(code[code{code(code{code()})}]));

If I wanted to make a fucking app or a website using fucking Haskell I'd do that.... at this point reading assembly code feels like heaven compared to this retardation... Why is this so popular?! WHAT DO YOU PEOPLE SEE IN IT?! Clearly it's not the aesthetics... it looks like a fucking frog vomit running down an emus leg, fuck that.... I don't even hate classic JavaScript, it's a good enough language and it does what I tell it to... but these ugly fucking frameworks like react, angular and whatever else uses this fucking format can go fuck right off. This is not the way JS is gonna get a better name for itself...

So:
Fuck Google

Fuck the marionette that designed the Android SDK

Fuck the Hellspawn the came up with the "functional-like" way of using JavaScript

Fuck everyone that thinks "JavaScript everywhere" is a good thing

And deeply future-fuck everyone that makes a new framework following any of these standards, stucks a .js at the end of the name and releases his hairball.js of an invention into the fucking world....

It's a mess... fuck everything android related...

I only develop UIs with react and only ever with functional components

I would actually DIE without my MacBook Pro 16”

I spend roughly 30 minutes a day trimming my beard. I’m a civilized man after all

I only drink Starbucks coffee, and only if it’s a triple pump latte

Ew what’s jQuery? Sounds like something my grandpa used

Omg really? Are you still using PHP in 2020?! Lame!

Gross. Windows is for n00bs and Linux is for nerds. macOS FTW

Post is comprised of quotes from a classmate who annoyed the living hell out of me

React developers, What do you think about the new hooks api?

Will you refactor your codebases to use functional components or just stick with classes (even though the react community is moving towards removing classes completely)?

I think its awesome as it reduces the bundle sizes if you use function components though. I have been working on an awesome project for a while and I'm being tempted to refactor the whole codebase to use functions instead of classes. What do you think?

Witch hunting:

I just spent the last 90 trying to fix a visual bug with the UI

I made a functional component to render pretty forms with minimal information in React
Turns out some random ass fields were not rendering with their respective lower borders

Refactored the shit out of the components
Actually got them to follow a strict styling

Two cups of coffee later it clicked: everything was perfectly functional, I just have a shitty small monitor and tried zooming in
WOULD YOU LOOK AT THAT, IT'S THE FUCKING BORDER I WAS LOOKING FOR ALL ALONG!

Don't be like me: check les differents view ports

I cannot even function right now with how angry I am. If you're a python developer, don't take offence to this unless it describes you.

All the python devs I have ever met so far are pompous arrogant cucks that can't even get out of their own way to save themselves. They make EVERYTHING so fucking complicated and complex that the whole point to a project becomes moot.

Instead of understanding HOW a thing works, their answer is ALWAYS rewrite it how THEY want it to work.

They have what we used to call "little-man" syndrome. They're so concerned that they aren't perceived as intelligent that they overcompensate by making the wildest and most fucked up changes to a project I have EVER seen.

They have gone so far as to break the original functional components of a project just to meet THEIR definition of a healthy python project.

I don't hate the language, but GOD DAMN I HATE THE DEVS.

If this describes you, fuck you. Seriously, just fuck off into whatever python hole you crawled out of and stay there.

Converting one of my older projects to use functional components and hooks instead of class components and prop drilling. It's nice.

Though now I have this useState:

const [ disembodiedHead, setDisembodiedHead ] = React.useState("");

Promise it's not as creepy as it sounds.

Anyone in here successfully using a pure FP language/ecosystem on their day to day?

I know of one of you that uses Scala, and myself I have an (admittedly) shitty application at work running in Clojure. These last two languages I mentioned are not pure FP.

I am talking about the likes of PureScript, Haskell, etc. Those mfkas.

If so,what is your experience working in said paradigm? I tried to keep my Clojure program as pure as possible, I failed, but enjoyed it.

And I know that FP is not a silver bullet, but in some scenarios when properly applied it can work beautifully. I also have React based applications with pure components, but Javascript itself is neither a functional(pure or otherwise) programming language, it merely supports functional paradigms.

Just wondering, no flamewars or anything like that, I just want to know your pros and cons.

Its not a product, but personal opinion working on react for the last 4 years and one thing is for sure Reacts functional components are shit to use compared to the class components. Specifically useEffect. React was never supposed to be written in a functional way when it first launched.

Ok, I'm actually raging at vuejs right now, and this is coming from my second year using it.

the fucking shit is weird.
functional components cannot use v-model.
functional components also cannot reference other components via components property, that child component needs either to be global or be injected (an ugly hack).

v-model behaves differently on checkboxes. checkboxes are fucking shit on vue. things update or do not update.

functional components with checkboxes? hahahahahaha.

vue 3 is taking an ungodly shitload of fucking amount of time.

fuck react, but im actually considering giving vue the middle finger as well.

started this product migration 2 months ago and regretting it, looking at svelte with curious eyes.

In React, OOP is now the old way of approaching react.js everybody doing functional programming/functional components.. this that the future ???

Class components, although verbose at times, are still far superior than functional components in React. The more I work with React, the more I believe that: Hooks are plain shit.

React, it's declarative way of doing things, and the functional programming methodology it prefers.

Realized how much I've moved on from for-loops and class/object instance to maps, filters and immutability/observers when I worked on a Laravel project after so long and found myself forced to do things in the, erm, "PHP" way, despite spending my initial year and a half of programming working exclusively in PHP.

Sure, there's Class Components and imperative techniques in React but I had blissfully settled into using the flexible nature of doing things enabled by both native JS and React, with hooks, Lodash/Ramda and (almost fanatically) pure functions

React Hooks question: those states we create in functional components, are they just for UI purposes or does it have use for overall the app? Please enlighten me!

Holy shit. I've been working on a project for the last few months. It's been going fairly well all things considered. We're currently at the tail-end of the project and are set to be dev complete next Friday.

We're on a headless CMS + Gatsby and decided to use a front-end framework (This is important to the story) to "speed development time."

PM comes to me yesterday and inquires about functional/visual QA on IE11. IE-What?! This framework I was told I had to use doesn't support IE11.. like.. at all, and now we need to support IE11, at the ass-end of this project, cause 60% of the traffic on their current site uses IE11? Oh come on!

So its looking like we get to re-write a few components from scratch. Then we get to try and fix the display issues for the other ones... FML, I was looking forward to being done with this so I could take a week off and go recharge before Thanksgiving garbage.

How do you think about unit testing/TDD when writing apps? (I'm working this at 3am so might be a bit messy... Just a thought I woke up to).

Whenever I write an app, I don't write unit tests but as I'm developing I may create test functions for specific parts that I run to validate a specific component is working before moving onto the next.

So first, when I get a problem, break it up into components based on the requirements. It's usually sort of input, processor, output sequence.

Where the processor is essentially the core app. And so I start coding it, referring to the input thru an interface, model objects, adding fields as I go along (assume no matter what the input, I will get these before the logic is called). I may add some more interfaces as well for other data I may need but I know won't be going in the first input.

So I write all the logic, functions needed to get a basic app to run that does what I am writing the app for.

Only then do I write a test functions passing in different parameters to make sure the logic and response is what I want and making fixes as necessary. At that point I basically have the simplest version of the app.
(I guess this is sort of like mocking?)

Then build outwards implementing and testing components as I go along and may do some simple refactoring/redesign. (I guess all these tests are functional then, have to start the whole app).

And finally when I have the basic requirements fully complete I will add the "nice to haves" on top via refactoring of specific logic in specific components. Again testing by running the app maybe with simple inputs.

I guess now I'm thinking how do you write unit tests/TDD if the app keeps changing (via adhoc refactorings) as you are creating it?

I am trying to isolate logic in React with functional components. Is it a bad idea to forwardref to a custom object that I use to expose actions? This way I could model the ref behavior from old class-based components where it was perfectly normal to represent a capability as a class method.

What are some great react projects utilizing hooks, functional components and possibly the context API.

Need some great ideas for projects from good sources. Need something where I can really LEARN. I mngood at following along YouTube videos . It gets me going then I get into Auto pilot mode. Where I can foreshadow what's gonna happen next. Please help!

1. Project ideas.
2. Great resources