745 karma · joined October 20, 2010
I expect more reports like this. LLM providers are already selling tokens at a loss. If everyone starts to use tmux or orchestrate multiple agents then their loss on each plan is going to get much larger.
Agree with you - I think when my colleagues have talked about boilerplate they really mean two kinds of boilerplate: code written once for project setup, like you describe, and then repetitive code. And in the context of LLMs, they talking about repetitive code.
I'm constantly surprised by developers who like LLMs because "it's great for boiler plate". Why on earth were you wasting your time writing boiler plate before? These people are supposed to be programmers. Write code to generate the boiler plate or get abstract it away.
I suppose the path of least resistance is to ignore the complexity, let the LLM deal with it, instead of stepping back and questioning why the complexity is even there.
>In the end of the day academia in general should stop relying on exams based on memorization of random facts and start using real world examples of what kind of work student would be working with as an employee.
I have an undergraduate degree and PhD in chemistry and I don't really think "blind memorisation" had much to do with my success. It will only get you so far.
I think there is also substantial within academia about the purpose of academia. I think a lot of academics might disagree that it is about preparing people to be employees.
I would try Tuple but to be honest we are fine on Code with Me.
Night and day compared to something like Linear.
I'm surprised at this statement. My team pair a lot - at least half of the time - and the majority is remote.
We find it much more comfortable to pair remotely on our own setups than crowded around a single desk and keyboard.
I wonder why our experiences are so different.
The major plus of having low or zero baseline caffeine consumption is that when you really need a jolt, a single cup will have the desired effect!
In my penultimate year I was struggling under a huge lecture and lab workload, working at the weekends, and partying too.
I developed stomach pain and went to the campus doctor, who sent me off to A&E (ER) with suspected appendicitis. My appendix was fine, but the doctors thought I might have a stomach ulcer. I discharged myself early to get back to the library, so never actually got a diagnosis!
I was drinking 3-4 cups of coffee and ~500mL knock-off Red Bull a day, eating a poor diet, and then drinking alcohol in the evenings. I went cold turkey and spent an entire weekend in bed with the worst headache imaginable.
I think I managed a few months before cracking and getting back on coffee. I quit cold turkey again a couple of times but in recent years I titrated off of it by gradually changing ratio of caffeinated to decaffeinated beans in my coffee at home. I drink 1 - 2 small cups a day now.
Might give quitting a go again.
Yesterday I heard Cory Doctorow talk about a bunch of pro bono lawyers using LLMs to mine paperwork and help exonerate innocent people. Also a big win.
There's good stuff - engineering - that can be done with the underlying tech without the hyperscaling.
I used to share your view, but what changed my mind was reading Hao's book. I don't have it to hand, but if my memory serves, she writes about a community in Chile opposing Google building a data centre in their city. The city already suffers from drought, and the data centre, acccording to Google's own assessment, would abstract ~169 litres of water a second from local supplies - about the same as the entire city's consumption.
If I also remember correctly, Hao also reported on another town where salt water was being added to municipal drinking water because the drought, exacerbated by local data centres, was so severe.
It is indeed hard to imagine these quantities of water but for me, anything on the order of a town or city's consumption is a lot. Coupled with droughts, it's a problem, in my view.
I really recommend the book.
dbt Cloud is an uncompelling product. Fivetran is convenient but absurdly expensive. Now dbt core development is just another marketing cost for Fivetran.
I'd really love to see everyone move on from the "modern data stack". dbt is a sticking plaster to a problem caused by orgs aggressively adopting SaaS products and choosing distributed software architectures without any thought about how to deal with the problem that your data models don't fit together and data is stored in 30 different places.
Considering how many developers still don't write tests, pair program, or do CI and CD (shipping multiple times a day) – all things Dave argues for – I don't think it is fair to dismiss him as the establishment or incumbent.
I'll pass. I'd rather have the battle-tested old thing, thanks.
If anything it is slow because it is a pain to navigate. I have browser bookmarks for my most frequented pages.
Emphasis added.
I have never worked anywhere that has done this. Humans have always reviewed every application.
I see what you’re saying, but a lot of Python users, especially those who have been using it pre-3, would say that this is unfortunate.
> I also think Django should just adopt these components and we would not have the discussion in the first place.
Oof, such a monoculture sounds terrible to me!
Unfortunately every team I’ve worked in hasn’t seen the light and prefers FastAPI/SQLAlchemy/Pydantic (before FastAPI it was Flask).
My theory is that the initial learning curves are different: with FastAPI it’s quick and easy. You barely have to read anything. Django has a steeper learning curve. There’s a lot of reading involved. Type hints aren’t a big thing in Django, but they are in FastAPI, and the average full stack dev seems to like them.
Later on it’s totally different of course. With FastAPI you’re building it all from scratch, and it’ll be much worse than the Django solution.