Lmao ok ill just follow best practices and end up inadvertently writing an orm from scrach then 🙆♀️
Introverts cannot comprehend introverts.
Hating on Lombok and setters simultaneously seems contradictory.
In an effort to make the post full of engagement bait, the dude ironically made it less engaging.
Remove every bullet point except Lombok, and you got yourself a proper flame war.
Whatever this guy supposedly architects, it ain’t software.
Ideal situation: single guy working from home, no pets. Neighbors describe him as “pretty quiet” or “I dunno.”
Golang outside of infrastructure
What does that even mean?
Golang is petty slow with a GUI I’ve found, a web UI works well but GTK or something like that is slow. Maybe that’s what he means?
Devops/IaaS/Kubernetes stuff.
He’s missing out on HUGO, Gin, Surf and Ebitengine just to name a few.
He wants all his infrastructure to be pure golang.
I read it to mean that he believes Golang should only be used for infrastructure and nothing else.
This is an assumption based on a structure of: if you [insert dot point] then we ain’t cool.
Allthough I only rarely exclude anyone from anything for any reason, I suppose one addition I would make to a list of mental farts I use to elevate myself, would be: people who communicate their ideas like a PowerPoint and expect to convey real meaning.
What I find crazy about X, is that even though it’s owned by Musk, a lot of Americans are quietly and conveniently ignoring it. People are losing their shit over Tesla and then posting about it on X.
I watched a YouTube video the other day where the presenter, who is a full time politically left content creator, was sharing his screen and discussing a Bernie Sanders X post, from within his own X account. It’s crazy.
Why anyone is still on that burning pile of trash, I will never understand. I mean, if you want to say anything longer than 280 characters long, you have to pay a premium. This is the opposite of ‘free’ speach.
Peace!
NGL I was on board at the first line. He lost me quickly after though
Software craftsman
Fart sniffer detected
Am I wrong or does that title he’s given himself directly contradict his dislike of code ownership? Or is it just he assumes he deserves credit for the code written by any of his subordinates?
that particular point likely refers to the fact that he prefers shared ownership: ie nobody should be “the one you go to for X part of the codebase”
Code ownership implies that 1) changes to that code are bottlenecked/gatekept by its “owner”; 2) code is siloed and there’s poor organizational collaboration culture.
“I am enabled to seek out the needed background and change what I need to move forward” vs “that’s not ‘our/my’ code, we can’t touch it. Let’s file a DEP ticket against that team and wait a few months”
Yeah, I threw up in my mouth a little when I read that.
He didn’t rule out BASIC so he good in my books.
Ew…
That’s: 10 PRINT “Ew…”
20 GOTO 10
This might be my type of job. I ssh into a server and build the backend using bash scripting in nano. HTML and CSS is also done using nano on the live server. No SCRUM needed. We have a large group of testers we refer to as “customers”, and they pay for the privilege.
Real devs write each http response by hand. If you use a server you’re a filthy casual soydev
Lol. Let’s ban accountability, refactoring, and debugging, never work alone, never coordinate, avoid productivity, and refuse ownership—then scream when things break, don’t integrate, and fall behind schedule.
“This is all your fault!” built-in. Why didn’t you intuitively know what myX is supposed to do and how it’s used?
Provocation just for “engagement” really. 102 comments so, to some degree, it works.
E: Guys, it’s satire. Lol.
Let’s ban
overshot your mark. maybe you misunderstood what you read and that’s why you’re so needlessly het up.
I don’t see any ban of accountability, refactoring or debugging, coordination, or endorsement of screaming.
I recognize most of these as specific antipatterns that get adopted because some manager read a blog or no one actually had a clue was “agile” meant.
I recognize most of these as specific antipatterns that get adopted because some manager read a blog
Go ahead. Point out the anti-pattern baggage.
There are enough coders on here from before the post-dot-com made mentors extinct that I’m sure they’d love your specificity.
Check my top level comment and several other replies on this post.
One I’ll mention here is “Tasks for testing and refactoring”. “Task” is the key word - testing and refactoring isn’t a backlog item that the product manager gets to deprioritize. (haha, like the product manager even realizes they are supposed to manage the backlog). It’s part of ongoing continuous codebase improvement and done whenever and wherever it’s needed.
I’ve been a software developer since 1997, I’d love to have a beer and shoot the shit with them!
Wow, the only one I agree with here is MongoDB (and probably Lombok, I don’t write Java), and that has more to do with their licensing issues than anything technical.
That’s pretty impressive.
Here’s my list:
- no-go list of languages - Java, PHP, Ruby, C++ (unless you absolutely need C++ for some domain)
- OOP - OOP should be isolated, not forced on every problem; many OOP advocates are dogmatic about injecting it everywhere
- waterfall - screw that noise, faster to market + faster feedback is generally better
That’s really it, and I’m totally willing to mentor someone who likes the above if they’re otherwise a good developer.
If you had to write Java you probably would like Lombok if you dislike boilerplate (it can build object constructors, comparators, and field accessor methods via annotation).
Java is boilerplate though. It’s finally getting almost tolerable with static imports, arrow functions/lambdas (whatever Java calls it), etc.
If I had to write Java, I’d push for Kotlin instead, after failing to convince management that there are much better options for the problem they need to solve.
That’s great! I wouldn’t want to work for him anyway.
Code Ownership
Lol did someone try and make him maintain the shitty code he wrote
Individual accountability
Team accountability is almost always better.
Group punishments so that the group will give sock soap to the individual. Best of both worlds
jeez dude you’re carrying a lot of baggage
Correct, but sock soap is the solution
more likely a reference to someone being the 1 person you go to for a particular part of the codebase like they own it
