I don't read/write code these days, I only instruct an LRM. But it's not because I think LRM code quality is perfect, or even good. And it's not because I think my instructions are always being perfectly acted upon -- I know they aren't.
The thing is: LRMs don't just write your code, they unlock new ways to control what you're doing and maintain understanding of your system, which are about as effective as reading code. You can better test your codebase, you can audit specific components, you can spin up visualizations, you can ask the LRM to red team, etc. You can do all of these things at high speed -- you couldn't before. The benefits of reading/writing code can now be achieved in new ways.
All in all, the ROI of writing code by hand is no longer looking good, not because LRMs got perfect but because they're so fast at doing things that you can develop new workflows around them, workflows that end up being more productive than the old workflows.
@frknasir@traversymedia Lol, sorry you took my argument personally, for a second I forgot I was on twitter, where ad hominem is the logical response to any form of criticizm.
I'm unable to take you seriously now so this exchange is over.
@frknasir@traversymedia These generalist takes are dumb, one can definitely go wrong with HTML CSS and VanillaJS, especially as a beginner
Important things like accessibility, SEO and potential scaling are easy to gloss over without helper frameworks to nudge in the right direction
_
It's truly remarkable how I conveniently forget everything as soon as anyone wants to see what I'm doing.
It's like a magic trick, but instead of pulling a rabbit out of a hat, I make my SQL skills disappear faster than you can say "SELECT * from table"
Daily meetings are a micromanaging shitshow.
Most people know these 15-minute stand-ups are useless. But they do them anyway because "that's how it should be."
One day, the corporate world decided that Scrum answered every problem. Daily meetings became popular. Everyone. Every day. No exceptions.
When did we become numb to how inefficient this is? How much time do companies waste every year in this charade?
The funny part is that Scrum sells these by telling us they are a way to avoid other meetings. You gotta be kidding me!
Unfortunately, I've participated in daily stand-ups for decades. If I were to compress these years into a single story, it would read like this:
• We are still waiting for some. Where is he? We can't start unless we are all here. We are late already.
• There's a manager in the meeting. We know she shouldn't be here. Who is going to tell her?
• We take turns reading from a JIRA board shared on the big screen. Everyone can read, but we still do it out loud. She wants to hear us say it.
• Yesterday wasn't a great day, but I won't admit it. Instead, let me tell her, "I'm making great progress" and "I'm getting closer than ever."
• We are all talking to her. She said this is a "safe space." We trust her, of course. Now, she is questioning anyone who isn't moving fast enough.
• 15 minutes in, and we are still here. Same as yesterday.
The first time I led a team, I stopped daily stand-ups. One of the first principles of getting shit done is "maximizing uninterrupted time." Daily meetings are in direct conflict with that.
Why should I force everyone to be at the same time and place while stopping everything else?
I asked everyone to write instead. Some people wrote every day. Some people, whenever they had something to say.
10x improvement overnight. For the project and the team.
I've talked to many people about this. Many tell me developers will never communicate unless you force them into a room daily. They say I shouldn't trust them to put in writing what they need to tell everyone else.
They may be right. They need a better team.