> "Requirements documents that were once a page are now twelve. Status updates that were once three sentences are now bulleted summaries of bulleted summaries. Retrospective notes, post-incident reports, design memos, kickoff decks: every artifact that can be elongated is, by people who do not read what they produce, for readers who do not read what they receive." Great article. The "elongation" of workplace artifact…
I just don’t read this crap. The problem solves itself since anyone sending me that isn’t going to bother to follow up about it anyway.
Appearing productive in the workplace
111–120 of 686 posts
Re: Appearing productive in the workplace
#112What is described here closely resembles my experience too. My company is full of managers who haven't written code in years. They hired an architect 18 months ago who used AI to architect everything. To the senior devs it was obvious - everything was massively over engineered, yet because he used all the proper terminology he sounded more competent to upper management than the other senior managers who didn't. When…
I saw something really similar happen at my last few jobs. 2 jobs ago vibe coding wasn't even viable but some of the people went so hard on making everything so much more bloated with LLMs it was so hard to get yes or no answers for anything. 1 line slack, 20second question would get a response that was 2 pages of wishy washy blog posts with no answer. Follow ups generated more hours wasted. My last job we watched a…
Re: Appearing productive in the workplace
#113Earlier quoted context omitted.
> Reminded me of when I had to be extra wordy to meet the 1000 minimum word limit for my high school essays. Minimum word lengths are the greatest dis-service high school and college have ever done to future communication skills. It takes years for people to unlearn this in the workplace. Max word counts only please. Especially now with AI making it so easy to produce fluff with no signal.
Minimum word lengths were really a terrible idea and I wonder what arguments were used to get all the teachers to buy into that system.
Re: Appearing productive in the workplace
#114> "Requirements documents that were once a page are now twelve. Status updates that were once three sentences are now bulleted summaries of bulleted summaries. Retrospective notes, post-incident reports, design memos, kickoff decks: every artifact that can be elongated is, by people who do not read what they produce, for readers who do not read what they receive." Great article. The "elongation" of workplace artifact…
man I see this on Jira a PM or BA is like "yeah I'll write that AC for you" giant bullet list filled in a bunch of emojis and checkmarks
Re: Appearing productive in the workplace
#115> "Requirements documents that were once a page are now twelve. Status updates that were once three sentences are now bulleted summaries of bulleted summaries. Retrospective notes, post-incident reports, design memos, kickoff decks: every artifact that can be elongated is, by people who do not read what they produce, for readers who do not read what they receive." Great article. The "elongation" of workplace artifact…
Re: Appearing productive in the workplace
#116Seeing the idea explored in such depth is great, I really am concerned about this.
Re: Appearing productive in the workplace
#117Earlier quoted context omitted.
I think for a lot of companies, AI is a destabilizing force that their managerial structure is unable to compensate for. When you change the economics to such a degree, you're basically removing a dam - resulting in far more stress on the rest of the system. If the leaders of the org don't see the potential downsides and risks of that, they're in for a world of hurt. I think we're going to see a real surge of compani…
I’m an LLM enjoyer who also thinks that ‘er ‘jerbs are safe and, taken to their logical conclusion, most LLM-stroking online around coding reduces to an argument that we should be speaking Haskell to LLMs and also in specs and documentation (just kidding, OCaml is prettier). But also, I do a little business. You’ve hit the real issue, IT management is D-tier and lacks self awareness. “Agile” is effed up as a rule, wh…
It's the mechanics that don't reference Google or the Haynes manual that are more likely to get it incorrect.
As a kicker, mechanics also have a pricing book for the task, they know how many hours a task will take on a certain car (rounded up for the most part).
Re: Appearing productive in the workplace
#118The most productive people seem to be the ones who are skeptical of AI but found compelling cases to use them for and aren't afraid to correct them.
Using LLMs/agents feels like bowling with bumpers but I'm the bumpers.
Re: Appearing productive in the workplace
#119Earlier quoted context omitted.
Have a second of critical thinking on this topic will make it abundantly obvious why this line of questioning is anti-education and anti-intellectual. You write in school to practice. No just composition, but grammar, spelling, individual sentences. Practice requires volume. Subject yourself to a classroom of kids that you must teach to write, and throw out minimums. Will some students do fine? Sure, of course, and w…
> Subject yourself to a classroom of kids that you must teach to write, and throw out minimums. Strawman argument; the correct thing to do is not to throw out minimum word count and leave it at that, rather to emphasize the role of brevity and concision while still being sufficiently thorough. It's widely understood that LOC is a poor measure for many coding purposes, so it shouldn't be controversial that word count…
Re: Appearing productive in the workplace
#120What is described here closely resembles my experience too. My company is full of managers who haven't written code in years. They hired an architect 18 months ago who used AI to architect everything. To the senior devs it was obvious - everything was massively over engineered, yet because he used all the proper terminology he sounded more competent to upper management than the other senior managers who didn't. When…
"hired an architect 18 months ago who used AI to architect everything" Huh? 18 months ago? I've been using it that long - it wasn't able to do that back then....