989 karma · joined July 18, 2020
I don't think a person without interest in literary analysis would make this comment. On the contrary, I'm specifically calling out building non-sensical tools with little practical uses because the author of the tool does not engage with literary works beyond the most superficial layer. And because I don't believe quantitive analysis of art is benificial to culture and society, but that's a broader subject.
Then why is the first example they present about organizing behavior lol
> scanned and analyzed a whole bunch of books and would let you call up really useful data on books. [...] Frankly, all of that sounds amazing. And amazingly useful. Even more amazing is that he built it, and it worked. It would produce useful analysis of books.
> This is all quite interesting. It’s also the kind of thing that data scientists do on all kinds of work for useful purposes. Smith built Prosecraft into Shaxpir, again, making it a more useful tool.
Author's general illiteracy aside, he's really giving the game away here. I can't even think about the ethical implications of the project, because why would I care to count the number of adverbs and passive voice in all books ever, and why would you need a state of the art LLM-powered AI to do it?
If that were true, then moving to a microservice architecture they'd need 5 million instances of the microservice that replaces the part of the monolith that required 5 million instances in the first place, plus a couple of millies for all the other services.
The worst place I ever worked at had mandatory "ticket refinement" - a feature or a bug couldn't be worked on until it had been through a "refinement session", in which everyone had to chime in, and the ticket wasn't considered refined until everyone on the team fully agreed with the implementation. Naturally over time, this devolved first into writing pseudo-code in Jira tickets and then into near-production code in a google doc overflowing with comments. Leaving that company I told my manager "this is a team of 4 'senior' engineers, I'd suggest you get one proper senior engineer and 3 typists". Nowadays, you could probably shove minutes from those meetings into copilot and call it a day.
Of course, the flipside of this was that comp was about on par with the market, and the perks were top-tier. If you're okay with doing the bare minimum while spending ~20-30 hours a week on total nonsense, it's probably the dream job.
By the rules of the game, the option of switching is asking you the question "Do you think you chose the correct door out of the three?". If you think you did, you don't switch. If you think you didn't, by rules of the game, switching will get you to the right door. Since you had a 33.3% chance to choose correctly and 66.6% to choose incorrectly, betting against yourself and switching is probably the correct choice.
I see very little reason in cancelling profitable projects. Also, framing my comment as a "misconception" is kinda indisgenious. This is a philosophical disagreement, hard to frame my point of view as objectively wrong.
It'll probably be in the same ballpark as a good transparency mode on headphones -- close to indistinguishable in small bursts, but long term causes alienation/lack of presence.
And transparency mode on modern headphones is a waste of time since you can just take them off. I agree both the demoed features suck and I don't want them in my conference calls, but stuff like that is a necessary bridge for a new product category. Hard to call that wasted effort.
> If you’ve worked more than 4 jobs in the last 4 years, you’re in the danger zone. Many companies will discard a CV quickly if we don’t think you’ll stick around until next year.
I am so tired of this conversation. At this point, all I can do is shut up and be grateful to be rejected by these people if I ever have a spotty resume.