wpasc
Joined 8 years ago
Joined 8 years ago
(i agree that maybe OP pointing that out is nitpicking, but to steelman the case, such inaccuracies are what code review would find and are the subtle bugs that might pass a code review and break prod)
> easily identifiable problems
sent me down. as soon as I parsed that line I stopped reading, and I tabbed back over to spot them
> people are sleeping on the ChatGPT Work/Codex
just in general. I find it to be far superior (imo) for all tasks atm. Claude just overdoes things in writing, coding, architecture, etc
> One caveat: my experience comes mainly from working on infrastructure and developer tools at large companies, on teams where engineers have a lot of bottom-up autonomy to influence their roadmaps. In a more top-down environment, there may simply be less room to work this way.
I wonder if the overall trend in tech is that engineers are experiencing less bottom-up autonomy and more top-down controlled environments. I would be curious to see how many tech companies (or the average engineer's experience) have changed from being tech led where engineers have autonomy to being more product management led. My suspicion without evidence is that the overall engineering autonomy has decreased over the years as the culture of tech has (in my opinion) shifted away from tech focus to more business, management, product focus with engineers just as the widgets who are tasked with fulfilling the goals of business, management, product.
all hypothesis, only anecdata
Two things to flag:
edit: as I keep reading the paper, I keep noticing some common sentence construction patterns, stylistic choices, and other little tics that I find frustrating because they are the very same things that I've been working on a few "writing-style skills" to get rid of