Appearing productive in the workplace
641–650 of 686 posts
Re: Appearing productive in the workplace
#642Earlier quoted context omitted.
The ambiguous "needs more detail" thing would lead to a lot of students making it too brief in good faith, too long in good faith and both be frustrated and angry. You can write really good mini essay on a topic. And you can write really good super long essay on the same topic. Demanding that students mind read is not a good strategy. Specifying expected length, checking for it is a good strategy. Teacher should also…
A good rubric would remove a lot of this ambiguity.
Re: Appearing productive in the workplace
#643Earlier quoted context omitted.
I cannot judge without more context. Depending on the one liner, the problem at hand, and overall situation that can be justified. A CLI is straightforward to create. A bash oneliner can be a chain of 5+ programs, each buffering the stdin/out, what if the CLI is doing the same operation via streams instead? Just a random example but that can easily be worth it
Sure, then there's a point where the extra taste isn't worth its cost. I just don't like the fictional straw man where an expert has somehow been brainwashed by AI into forgetting everything they ever knew.
Because I don't think I've ever heard anyone say an expert gets brainwashed by AI into forgetting everything they ever knew. Maybe losing some skills that require regular exercise. Or get lazy about implementations when spawning dozens of super useful agents. But come on. Don't build your strawman out of a fictional strawman.
Re: Appearing productive in the workplace
#644> The first is when novices in a field are able to produce work that resembles what their seniors produce [...]. > The second is when people generate artifacts in disciplines they were never trained in. There is a third shape. Experts who have become so reliant / accustomed to AI that it dilutes their previously sharp judgment and, importantly, taste . I am seeing more and more work produced by experts which seems st…
Re: Appearing productive in the workplace
#645Earlier quoted context omitted.
This paragraph hit home with me as well. I work at a large tech company that's a household name and the practice of using AI to pad out design documents has become totally out of control over the last 4 or 5 months. Writing documentation is arduous and a little painful, which as it turns out is a good thing as it incentivizes the writer to be as succinct as possible. Why the fuck should I -- along with five other eng…
I see it even on my GitHub project, issues and pull request comments get longer, responses get longer, all generated by ai and read by ai. This text is no longer for human consumption, but to provide context to ai. See also this video from Nate B Jones: https://youtu.be/FDkvRl1RlT0?si=WUK2WJTXvKAWKD0r
We have never needed to "move slow and fix things" more than right now.
Re: Appearing productive in the workplace
#646Earlier quoted context omitted.
> Professional formatting, length, and clear prose are no longer indicators of care and work quality (they never were, but in the past, if someone drafts up a twelve page spec, at least you know they care enough to spend a lot of time on it). I feel the loss of this signal acutely. It’s an adjustment to react to 10-30 page “spec” choc-a-block with formatting and ascii figures as if it were a verbal spitball … because…
It is worse because the signal is buried in the noise.
Re: Appearing productive in the workplace
#647Earlier quoted context omitted.
Sure, then there's a point where the extra taste isn't worth its cost. I just don't like the fictional straw man where an expert has somehow been brainwashed by AI into forgetting everything they ever knew.
Wait... Did you just fictional strawman a fictional strawman? Because I don't think I've ever heard anyone say an expert gets brainwashed by AI into forgetting everything they ever knew. Maybe losing some skills that require regular exercise. Or get lazy about implementations when spawning dozens of super useful agents. But come on. Don't build your strawman out of a fictional strawman.
Re: Appearing productive in the workplace
#648Earlier quoted context omitted.
Everyone's job is to please their manager. Their job is shipping functional product features only if that's what their manager likes. In functional companies, that should be the case. There aren't many functional companies.
We need to make companies financially liable for data leaks.
Re: Appearing productive in the workplace
#649Earlier quoted context omitted.
>> The first is when novices in a field are able to produce work that resembles what their seniors produce [...]. > The second is when people generate artifacts in disciplines they were never trained in. This phrasing made me think of Baudrillard: https://en.wikipedia.org/wiki/Simulacra_and_Simulation , in particular "Simulacra are copies that depict things that either had no original, or that no longer have an origi…
I bought this book a year ago but have not read it. It's one of those books that requires effort from the reader, which these days seems in low supply for me. :) I'll have to give it another try. Recently I commented that: Artificial intelligence produces artificial results. I liked the double-artificial but I wasn't happy with the meaning. Perhaps Simulacra is more accurate? I will see :)
Kinda takes the effort out so you just gotta veg while reading/listening and following along
Re: Appearing productive in the workplace
#650I watched a video of some (unemployed) programmer lamenting over the current job situation market. He had been coding for a good while, but had recently been laid off. The vid was mainly concerning the searching and interview process, but it also did highlight something I find somewhat true and important: Right now we're in a gold rush. Companies, that be established ones or startups, are in a frenzy to transform or…
If anything, the current era looks like how 1995-2015 was for me. Back then I was not in the “nitpicker’s radar” yet. I was working in small teams and shipping like crazy, sometimes fixing small bugs literally in seconds. Things worked, were stable, made money, teams were fun and code and product had quality. The post-Thoughtworks, post-Uncle-Bob world of 2015-2025 was absolute hell for a maker. It was 100% about per…