Which is why he doesn’t have a company of his own. He’s a terrible leader.
LinkedinLunatics
A place to post ridiculous posts from linkedIn.com
(Full transparency.. a mod for this sub happens to work there.. but that doesn't influence his moderation or laughter at a lot of posts.)
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.
I’m pretty in-line with all these.
“guru”-driven, fad, and ineffective management processes, misunderstanding and corporatization of low-overhead planning tools, rather crappy (and faddish) languages, and not putting team first - all bad things.
This feels like a facetious post because what. There’s no way he’s serious
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.
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.
Erlang/Elixir doesn't have muteable variables/types. Appending to a list would just create a "new" lists.
There are non-mutable lists and every other data type.
https://docs.scala-lang.org/overviews/collections-2.13/overview.html
https://docs.scala-lang.org/overviews/collections-2.13/concrete-immutable-collection-classes.html
“for… i++” is easily replaced with a foreach, range, iterable, etc… in any language of reasonable capability.
When you don't have a downvote button, all you get is an echo chamber
- 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 have for years been pumped to create a sql only side project or sql + frontend
No, just write a repository to expose domain operations and implements them using SQL directly. Trying to fake OO object graphs against a RDBMS with a super-complex and leaky ORM is just painful.
Would you classify GORM that way?
i prefer going GORMLESS
Groovy’s ORM? I recall it being Hibernate under the hood and I had to fight with it to avoid common problems like hidden IO and N+1 query blowups (iterating over a set of results and then touching the wrong property means you are making another network call for each), learning its particular DSL for schema definition and associations, and not having a way to represent any but the simplest SQL constructs. The usual ORM stuff.
To the extent that you can write a syntax-checked SQL statement and it deserializes the results into some collection of row objects, it’s fine. But that’s not the “ORM” part.
GORM is Go ORM
I have not used that GORM, but ORMs have those problems generally.
Code Ownership
Lol did someone try and make him maintain the shitty code he wrote
Individual accountability
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.
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?
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.
Good riddance.
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.
That's great! I wouldn't want to work for him anyway.