And I mean, go tell your leadership "Those projects that used to take us a full quarter? Now we can do them in 6 weeks." You don't get the rest of the quarter to stabilize your codebase. Now you jam 2 releases into the quarter.

Big bang prototypes have been pretty awful, even after feeding the LLMs huge documents / wishlists / descriptions of how it should work, etc. Part of the experiment was giving LLMs some leeway to make product decisions with a lot of north star guidance, but AFAICT they are really bad at this. I also tried basic bottom-up efforts, which have been better but obviously more tedious. Now I'm trying to find a more scalable bottom-up approach that is more LLM-accelerated

It certainly had its share of toxic traits, but it was at the "what place doesn't?" level.

Maintaining Elasticsearch isn't free, but picking an underpowered db and having to port to the right one is also quite time consuming.

Comments URL: https://news.ycombinator.com/item?id=48192131

Points: 3

# Comments: 0

I'm relying purely on memory, but all of the reasons were super public at the time. The internal Java editor tooling team decided that they weren't investing any more time into Intellij. And then a few months later, the Android team relaunched Android Studio using Intellij with full internal support. The existing Java tooling squad put up some amount of fuss saying that they had already made the decision, and the Android team gave a long and diplomatic response that could be compressed down into, "we don't report to you and we don't care what you think." This coincided with the entirety of Google becoming mobile native, so the mobile team were given free rein to call the shots.

> IMO IntelliJ never worked very well in google3

YMMV, we had some people in Docs/Drive who invested a lot of time into making Intellij usable for everyone, and following their system, it worked way better for us than Eclipse did. All of the "Let me sing you the song of my people ::UI freezes::" memes were very true in my experience.

Here's how a big tech reporting chain sees this situation when everything is smooth sailing: "We're growing 3x year-over-year? After 2 years, the cost will be an order of magnitude higher no matter what solution we pick. The constant factor doesn't matter that much. But we have such an incredible roadmap that we will book more than an order of magnitude of revenue, backed by this new ledger project. The cost will always be a nonissue because of growth."

And then 2 years go by, and this incredible product growth adds a bunch of ledger entries that weren't there 2 years ago, someone nudges your reporting chain with the question, "this is pretty expensive.. what gives?" and then someone with a good combination of social and technical skills points out that a migration to your existing storage solution would be a cost effective way to continue growing.

At every step of the way, everyone is generally happy with what's going on.

Random observations from my first one: - presenting my idea visually helped crystallize my thinking in a way that writing doesn’t. And writing was already very good at crystallizing my thinking. - even making a bad video was a lot of work - making a video presentable is a deep subject. Subtle changes were throwing off my setup. Now I understand why so many influencers are fitness and lifestyle; the demand side is obvious, but when you’re already camera-ready you have a huge advantage on the supply side - described something I built felt natural. I do that for a living. The intro was like 45 seconds and took me like 45 minutes to film because it was acting and I don’t know how to do that - learning about video editing features had an immediate payoff because video is so long

[0] I’m posting the videos at https://m.youtube.com/@bitlog-dev . I said if the first one got to 100 I’d commit to making at least 10, and I just crossed that threshold