Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
Search - "catharsis"
Fun day, lots of relief and catharsis!
Client I was wanting to fire has apparently decided that the long term support contract I knew was bullshit from go will instead be handled by IBM India and it's my job to train them in the "application." Having worked with this team (the majority of whom have been out of university for less than a year), I can say categorically that the best of them can barely manage to copy and paste jQuery examples from SO, so best of fucking luck.
I said, "great!," since I'd been planning on quitting anyways. I even handed them an SOW stating I would train them for 2 days on the application's design and structure, and included a rider they dutifully signed that stated, "design and structure will cover what is needed to maintain the application long term in terms of its basic routing, layout and any 'pages' that we have written for this application. The client acknowledges that 3rd party (non-[us]) documentation is available for the technologies used, but not written by [us], effective support of those platforms will devolve to their respective vendors on expiry of the current support contract."
Contract in hand, and client being too dumb to realize that their severing of the maintenance agreement voids their support contract, I can safely share what's not contractually covered:
- Stream based programming
- Angular 9
- Any of the APIs
- Dotnet core
- pretty much anything not in a commit
I'm a little giddy just thinking about the massive world of hurt they've created for themselves. Couldn't have happened to nicer assholes.6
A most cathartic feeling: when I get to remove a huge block of commented code that isn't necessary. 😌4
While reviewing a PR from one of our newer FE devs, I ended up spending more time than I would like mulling over its composition. The work was acceptable for the most part; the code worked. The part that got me was the heavy usage of options objects.
When encountering the options object pattern (or anti-pattern, at times) in complex scenarios, I have to resist the urge to stop whatever I'm doing and convert it to the builder pattern/smack them in the head with a software design manual. As much as I would like to, code janitor is one of the least valuable activities I engage in daily, and consistently telling someone to go back to the drawing board for work that is functional, but not excellent is a great way to kill morale. Usually, I'll add a note on the PR, approve it, add a brown bag or two on that sort of thing, and make attendance mandatory for repeat slackers. Skills building and catharsis all rolled up in a tiny ball of investing in your people.
Builders make things so much cleaner; they inform users what actions are available in a context; they tend to be immutable, and when done well, provide an intuitive fluent interface for configuration that removes the guesswork. As a bonus, they're naturally compositional, so you can pass it around and accumulate data and only execute the heavy lifting bits when you need to. As a bonus, with typescript, the boilerplate is generally reduced as well, even without any code generation. And they're not just a dumping ground for whatever shit someone was too lazy to figure out how to integrate into the API neatly.
They're more work in js-land, sure; you can't annotate @builder like with Lombok, but they're generally not all that much work and friendlier to use.9
I've been struggling with some financial issues lately. I haven't told this to my family bc I am helping my mom with money, hat wouldn't help.
Sadly, I got two general tickets for WebSummit 2019 and I thought "okay, I am nearby Portugal rn, somebody of my circle could go with me and have some fun, I feel so blue..."
No one. Not a single one. Nobody.
"Maybe with those Telegram groups of JS developers..."
Maybe it sounds like some fraud or something, so they didn't answer. I even mentioned to an old entrepreneur friend of mine, and he didn't even answer me.
Disheartened is the word for today. I don't know, I am not expecting that people can join this adventure just bc is awesome, we all have bills to pay, but at least an answer would be fine.
I know it is not a fun story, and there are people in worse situations than mine. I just wanted to do some catharsis bc I lost my laptop.
I still have bills, two tickets, and a new kind of miserable mood.
Thank you for reading.2
To abstract your case,
Full of the catharsis
And exceptions to face.
Didn't commit, oh wait,
More trouble? One reset.
We return and all hail
This programming mindset!2
Y'know, there are some things that are timeless. Like bug severity arguments. We don't have a "likeliness of occurrence" parameter in the bug database. We just have "severity if it occurs". You have to classify it as such. The bug database IS NOT FOR RISK MITIGATION ACTIVITIES IT'S FOR FIXING THE FUCKING SOFTWARE!!! STOP MAKING THESE DAMN MEETINGS TAKE 30 YEARS BY QUESTIONING THE SYSTEM THAT WAS ESTABLISHED IN THE BEFORE TIMES BY PEOPLE WHO ARE ABOVE YOUR PAY GRADE!!! TINDER BOX!!! MATCH!!! GODS DAMMIT!!!