The first Tesla was based on a Lotus Elise. It was stunningly good looking. It changed people's minds that an electric car had to look like a glorified golf cart.
Later cars from Tesla looked more generic but still like looked like regular cars.
The cybertruck seems like a throwback to the old electric cars that looked like something out of nerd's sketchbook.
The competition isn’t very fierce but he sure did squander his advantage in the EV segment to get beaten to market by a company that had never shipped an EV before
Rivian selling the first EV pickup truck even after Elon’s announcement of the cybertruck is pretty embarrassing
The closest alternative that I've found to Plexamp is MusicAssistant. It's still really rough around the edges as a full replacement. For example: Smart playlists are lacking and/or don't work at all; "Recently Added Albums" goes by file modified time and not when it was actually _added_ (and they fought me on this saying I'm wrong that it doesn't seem right)
I can't read any of the text on that page other than the headings. Is that what makes it modern? I assume the stack mentioned in the blog post is vibe-slop as well.
I wanted to try my hands at a monochromatic website and chose two shades that were far enough apart to pass a AAA contrast rating for accessibility. I'll try to improve it soon.
My eyes aren't particularly bad, not at the point where I need glasses to read books, program or anything, but I'm at 160-170% zoom before it's comfortable to read. HN is the same... so it might just be me.
My work Slack channels are ghost-towns. People are logged in, but they're never saying anything. I often find myself wondering if anyone is even working. PRs have their names on them, even the review comments are posted from _their_ accounts, but it is obvious that Claude wrote everything from the code, the unnecessarily verbose change summary, to their comments. Even their replies to my change requests start with "You're right — …".
I miss the days when the engineering Slack channels had long threads of new and interesting ways to do things, discussions of something we could do next to make work easier or fix long-standing issues. We used to build up our own knowledge of who was good at specific things, what they'd be interested in working on. Now everyone just has their slop-machine spit out every piece of a change for the entire stack without paying any attention to the details.
Fwiw I work at a company where engineers use AI heavily to produce the majority of work outputs but we also have a Slack that's just as lively as ever and plenty of evidence of humanity. Your experience sounds bad and you may be able to find a better one! It's not all bad everywhere.
How established is your team? I can see how teams that existed from the pre-LLM era can maintain their vitality, but would expect newer teams to struggle a lot more. Also, remote or in-person?
I don't want to hear about the state of your Confluence (or equivalent), if you do use it!
Also one more thing I started noticing is unnecessarily detailed comments in code, complete with issue numbers. And some of that belong in version control commit (IMHO).
I've used git-bug[1] for issues and it works pretty well. The web-ui is lagging behind and PR support would be everything you'd need to ditch a central-hosted web instance.
I really wish this weren't the case, but I'm afraid that we're heading to a place where if we flood reports to officials, they'll just jump on calling bike lanes "DEI" and take them out.
Depends on the city. In Philadelphia, the opposite thing happened: proposed bike lanes along half of Washington Ave. were blocked by a city council member on the grounds that "only white people ride bikes" and "bike lanes cause gentrification." It was touted as an "equity win."
This councilmember is now the President of the Philadelphia City Council.
reply