Liking any of these indicates a belief system I don't agree with
Liking any of these indicates a belief system I don't agree with
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”
Yeah, I threw up in my mouth a little when I read that.
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.
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
more likely a reference to someone being the 1 person you go to for a particular part of the codebase like they own it
Just build whatever you want on prod and disappear after the deadline so they can never ask you to update your code
Sorry the developer you are calling is out of scope.
And write all Code in The most complicated and unreadable way possible. Dont use comments.
There are two types of software engineers: those who are anxious and those who are narcissistic and grandiose. This guy is easy to place in the latter category.
I was so happy when I got a job working with a guy who was super chill and a genius to boot, such an impossible combination to find.
Our mantra was pretty much do the best possible thing to reach the widest possible audience, nothing is off the table and no user is left behind completely. I learned such a wide variety of skills there. It went great for nearly a decade before everything went to shit because my guy had left and I was left to deal with a 3-1 managerial hell.
Whatever this guy supposedly architects, it ain't software.
- ORM's
- Place ALL of the business logic in stored procedures.
- Eliminate the backend.
- Make the front end connect directly to the database.
Profit- Introduce tons of bugs and terrible performance.
- Database is compromised within five minutes of going live.
I'm confused. Are you saying all of that is a consequence of not using ORMs? Because if so, that's absolutely not true. ORMs truly are complete trash.
Sounds like you were hurt by an ORM.
One huge benefit of an ORM is that it does type checking. it makes sure your tables exist, relationships are valid, etc, and it makes easy things easy. If you add a column, it'll make sure it gets populated, give you decent error messages, etc.
As long as you use a proper repository pattern setup and isolate DB interactions from the rest of the code, how you construct the queries is completely up to you. I try to use DTOs to communicate w/ the repo layer, so whether an ORM is used or direct SQL queries is largely an implementation detail.
I have for years been pumped to create a sql only side project or sql + frontend
Please don't. I self-host actual budget, and they compile SQLite to WASM to use it in the FE. That just feels... wrong.
When you don't have a downvote button, all you get is an echo chamber
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.
Golang outside of infrastructure
What does that even mean?
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!
Hating on Lombok and setters simultaneously seems contradictory.
This feels like a facetious post because what. There’s no way he’s serious
From my own professional experience (which covers various industries) if the guy works in Startups making B2C, this wouldn't be overly surprising.
There is a very special kind of mindset that's highly likely to develop when you're the guy with 5 years experience surrounded by basically kids, in an industry were the path for "winning" is shameless self-promotion, who never worked outside that environment and whose customers are this vague anonymous crowd (worse when they're mainly fanboys) - in the absence of professional references to compare yourself with, without hard feedback from users and customers, surrounded by people for whom making software is entirely "make it up as you go" (rather than, you know, and engineering process) and in a business domain were the biggest boaster get the biggest rewards, lots of people start breading their own farts and calling it perfume.
NGL I was on board at the first line. He lost me quickly after though
No mutable types? So like.. no lists? no for ... i++?
I get that there are alternative approaches, but I don't quite see why you'd want to go to that extreme with this idea? It's useful for some applications but even for a simple video game it's likely not helpful.
It's perfectly possible to work without mutability.
Is it desirable to be entirely without it? Probably not, but leaning immutable is definitely beneficial.
Yeah, copying can totally screw you over. Mutability is fine, just make sure it's safe (e.g. what Rust does).
Pure functional programming is often like this.
Erlang/Elixir doesn't have muteable variables/types. Appending to a list would just create a "new" lists.
Good riddance.
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.