I’ve come across this analogy that I think works well:
Using an LLM to do schoolwork is like taking a forklift to the gym.
If all we were interested in was moving the weights around, you’d be right to use a tool to help you. But we’re doing this work for the effect it will have on you. The reason a teacher asks you a question is not because they don’t know the answer.
> I should hope that the purpose of a class writing exercise is not to create an artifact of text but force the student to think; a language model produces the former, not the latter.
It's been incredibly blackpilling seeing how many intelligent professionals and academics don't understand this, especially in education and academia.
They see work as the mere production of output, without ever thinking about how that work builds knowledge and skills and experience.
Students who know least of all and don't understand the purpose of writing or problem solving or the limitations of LLMs are currently wasting years of their lives letting LLMs pull them along as they cheat themselves out of an education, sometimes spending hundreds of thousands of dollars to let their brains atrophy only to get a piece of paper and face the real world where problems get massively more open-ended and LLMs massively decline in meeting the required quality of problem solving.
Anyone who actually struggles to solve problems and learn themselves is going to have massive advantages in the long term.
Looks like you found the not-so-secret repository we're using to prepare for a broader announcement :)
Please be aware this is pre-alpha software. The current version is 0.0.0a6 and the releases so far are all in service of validating our release process. We're excited to get this in people's hands, but want to set the expectation that we still have a lot of work left to do before this is production ready.
next level would be to hook these "platoons" together physically and then centralize the propulsion in a super efficient package. And then we could move them off the highways and onto specialized "tracks" that guarantee they don't deviate from the planned routes.
speculative, alien technology, admittedly, but some day our scientists will figure it out i bet!
I gave away the “ty” project name on pypi to Astral a week or so ago. I wanted to use it for a joke a few years ago but this is a much better use for a two letter project name. They agreed to make a donation to the PSF to demonstrate their gratefulness.
I didn't see anyone mention the McMaster-Carr website [1]. It may not be the "densest" out there, but it's clean, functional, and nicely presents a lot of information at once.
It's wild to me that Jetbrains has been making so many top-tier IDEs, languages, runtimes and other developer products for 25 years now and is valued at maybe $5B, meanwhile we have months-old "pre-revenue" startups releasing AI coding wrappers and raising money or being bought out for twice that.
There's a quote I learned when doing theatre, which I've seen attributed to either the stage magician Doug Henning or possibly Stanislavski, describing the process of art as taking something that's difficult and making it habit, then taking something that's habitual and making it easy, and then taking something that's easy and making it beautiful.
For example, as an actor, you learn your lines by rote (they become habit), then you gain an understanding of the character's motivations (remembering the lines becomes easy, because of course that's what your character would say), then you work to tune your performance so the audience shares in the emotion and unspoken meaning of the lines (that's beautiful/art).
As this relates to software, I think it goes something like: you learn the magic incantation to make the computer do what you want (solving a hard task becomes habit), then you learn why that incantation works (solving it becomes easy), then you figure out better ways to solve the problem, such that the original friction can be removed completely (you find a more beautiful way to solve it).
Last year I took a smartphone holiday for 4 months (switched to a dumbphone). It was a fantastic time and I regret "falling off the wagon" and getting a smartphone again.
I noticed a huge number of benefits, but one of the most surprising was that it forced me to confront a number of difficult decisions.
There were a few times in which I was bored (waiting at the passport office, sitting on a plane) in which I started to think about decisions I had to make that were very difficult in ways that caused me anxiety: firing a person I'm good friends with, shutting down a company, stuff like that.
I realized that ordinarily I would simply refuse to engage with the decision: I'd get on my phone or "get busy" somehow and so simply postpone thinking about the issue indefinitely.
But when you're stuck at the passport office for 2 hours with nothing to do, you can't but help think about the thing that is top of mind, anxiety be damned.
For someone that is prone to anxiety around certain topics (conflict avoidance, "disappointing" people, etc) having times in which I was forced to engage with the topic had truly enormous benefits.
The one thing that sold me on Rust (going from C++) was that there is a single way errors are propagated: the Result type. No need to bother with exceptions, functions returning bool, functions returning 0 on success, functions returning 0 on error, functions returning -1 on error, functions returning negative errno on error, functions taking optional pointer to bool to indicate error (optionally), functions taking reference to std::error_code to set an error (and having an overload with the same name that throws an exception on error if you forget to pass the std::error_code)...I understand there's 30 years of history, but it still is annoying, that even the standard library is not consistent (or striving for consistency).
Then you top it on with `?` shortcut and the functional interface of Result and suddenly error handling becomes fun and easy to deal with, rather than just "return false" with a "TODO: figure out error handling".
Windsurf and Cursor feel like temporary stopgaps, products of a narrow window in time before the landscape shifts again.
Microsoft has clearly taken notice. They're already starting to lock down the upstream VSCode codebase, as seen with recent changes to the C/C++ extension [0]. It's not hard to imagine that future features like TypeScript 7.0 might be limited or even withheld from forks entirely. At the same time, Microsoft will likely replicate Windsurf and Cursor's features within a year. And deliver them with far greater stability and polish.
Both Windsurf and Cursor are riddled with bugs that don't exist upstream, _especially_ in their AI assistant features beyond the VSCode core. Context management which is supposed to be the core featured added is itself incredibly poorly implemented [1].
Ultimately, the future isn't about a smarter editor, it's about a smarter teammate. Tools like GitHub Copilot or future agents will handle entire engineering tickets: generating PRs with tests, taking feedback, and iterating like a real collaborator.
i love this. A startup I was at during early COVID times got acquired into Hewlett Packard Enterprise, so we all became HPE employees with HPE addresses. There was a similar form there to request "ryancnelson"@hpe, etc...
One of my co-workers got cute and asked for "root@hpe.com" .... And boy, there's a lot of cron jobs running at HP.
Just my opinion but, server‑side rendering never really went away, but the web is finally remembering why it was the default. First paint and SEO are still better when markup comes from the server, which is why frameworks as different as Rails + Turbo, HTMX, Phoenix LiveView, and React Server Components all make SSR the baseline. Those projects have shown that most dashboards and CRUD apps don’t need a client router, global state, or a 200 kB hydration bundle—they just need partial HTML swaps.
The real driver is complexity cost. Every line of client JS brings build tooling, npm audit noise, and another supply chain risk. Cutting that payload often makes performance and security better at the same time. Of course, Figma‑ or Gmail‑class apps still benefit from heavy client logic, so the emerging pattern is “HTML by default, JS only where it buys you something.” Think islands, not full SPAs.
So yes, the pendulum is swinging back toward the server, but it’s not nostalgia for 2004 PHP. It’s about right‑sizing JavaScript and letting HTML do the boring 90 % of the job it was always good at.
Something that really frustrates me about interacting with (some) people who use AI a lot is that they will often tell me things that start “I asked ChatGPT and it said…” stop it!!! If the chatbot taught you something and you understood it, explain it to me. If you didn’t understand or didn’t trust it, then keep it to yourself!
> "Cardinal George of Chicago, of happy memory, was one of my great mentors, and he said: 'Look, until America goes into political decline, there won't be an American pope.' And his point was, if America is kind of running the world politically, culturally, economically, they don't want America running the world religiously. So, I think there's some truth to that, that we're such a superpower and so dominant, they don't wanna give us, also, control over the church."
The relevant part: "The ALICE analysis shows that, during Run 2 of the LHC (2015–2018), about 86 billion gold nuclei were created at the four major experiments. In terms of mass, this corresponds to just 29 picograms (2.9 ×10-11 g)."
Just need to scale it by trillions to make 1 ounce, but transmutation of lead to gold - the dream of many alchemists - is now just a by product of particle accelerators.
My frustration with using these models for programming in the past has largely been around their tendency to hallucinate APIs that simply don't exist. The Gemini 2.5 models, both pro and flash, seem significantly less susceptible to this than any other model I've tried.
There are still significant limitations, no amount of prompting will get current models to approach abstraction and architecture the way a person does. But I'm finding that these Gemini models are finally able to replace searches and stackoverflow for a lot of my day-to-day programming.
I worked on the design of wireless USB chips around 2008 - 2010. They worked - you really could get USB 2.0 full rate connections wirelessly and we had some neat demos.
I would say the major problem it had with adoption was that wired USB also provided power. (A lot more people use usb to charge their phone than to sync their phone.)
So great - wireless connectivity... but you still have to plug the device into a cable at some point (or have replaceable batteries), which makes the value proposition a lot less clear.
Beyond that it suffered from the usual adoption chicken-and-egg problem. Laptop manufacturers didn't want to add it because it was an expense that didn't drive sales since there weren't any must-have peripherals that used it, and peripheral manufacturers didn't want to make wireless usb devices since they couldn't be used with a standard laptop (at least not without a WUSB dongle - which raised the cost).
Recently I met some people that were constantly filming and taking pictures of everything. It was ridiculous IMO, for the same reasons OP mentions.
This is not new. For me, it began with the rise of the smartphone. So I made it a point not to waste my time photographing things.
10 years later, I regret having essentially no pictures of anything. In particular, no "good" or "frameable" pictures (blurry pictures from funny angles don't count...). Especially from important moments. Yes, I was there living the moment. But with a picture, I could relive it for a bit.
It's not hard to find the balance, though, I guess. You don't have to constantly be filming everything. Maybe just get the group together for one picture at the end of the event and that's it. Good enough.
That's what'll I try from now on at least. Report back in 10 years...
It seems like they're attacking the wrong end of the problem by trying to detect fake students in the classrooms. If the issue is that people are signing up for financial aid and then disappearing with the cash they'd be better off making sure that the people who get financial aid actually are who they say they are before sending them money, or better yet stop giving cash as financial aid and instead give some type of credit that can only be spent on/at the school.
Once scammers can't get access to the money the problem of bots in the classroom will mostly go away.
Our company just got a warning that we have sixty days to release something on Play or have our developer console account closed. The email made it pretty clear that Google wants developers to continuously push new versions to customers. We have no new features nor bug fixes in backlog. There is nothing to update.
The only purpose of our software is to control hardware that our company makes. Nobody uses it for fun, they use it because they have to. If I had a say, I'd automate even larger parts of the customer workflow.
(Yes, at first we released a mobile PWA but ran into limitations related to push notifications and MDM support. We then created the native app, but our customers cannot remotely load APKs not signed by Google).
I can't find the article anymore but I remember reading almost 10 years ago an article on the economist saying that the result of automation was not removal of jobs but more work + less junior employment positions.
The example they gave was search engine + digital documents removed the junior lawyer headcount by a lot. Prior to digital documents, a fairly common junior lawyer task was: "we have a upcoming court case. Go to the (physical) archive and find past cases relevant to current case. Here's things to check for:" and this task would be assigned to a team of junior (3-10 people). But now one junior with a laptop suffice. As a result the firm can also manage more cases.
Article is interesting on the whole (I have no experience with "professional" work, and would love for suggestions as to how to be more familiar), but I latched onto this nugget:
> Our vision at Meanwhile is to build the world's largest life insurer as measured by customer count, annual premiums sold, and total assets under management. We aim to serve a billion people, using digital money to reach policyholders and automation/AI to serve them profitably. We plan to do with 100 people what Allianz and others do with 100,000.
Completely separate from the potential ethical issues and economic implications of putting 100k people out of a job, I see one very concrete moral problem:
that the only way to provide dispute resolution and customer service to 1B people with only 100 employees is by depriving them of any chance to interact with a human, and forcing all interaction with the company to go through AI.
That, to me, is deeply disturbing, and very very difficult to justify.
On the off chance you're interested in school lunches I highly recommend watching videos of Japanese school lunches on YouTube. There's a bunch out there now and if you were raised in the American system it will probably blow your mind. The idea that lunches can be freshly made, on site, out of healthy ingredients and children are active participants in serving and cleaning up is just crazy. When I encountered it for the first time I felt like a big part of my childhood had been sold to the lowest bidder.
I've already asked a number of colleagues at work producing insane amount of gibberish with LLMs to just pass me the prompt instead: if LLM can produce verbose text with limited input, I just need that concise input too (the rest is simply made up crap).
I don't disagree with the article, but after working in big tech, two HN startups, a couple unicorns and others, in two continents, I don't really find this too actionable.
In the last ten years (and even in the 20-people HN startups), the day to day work of engineers has become so incredibly specialised and divorced from the needs of decision-makers and the customers that there is almost nothing I can do to influence whether someone views me as doing my job or not. Mainly because of the presence of Product Managers that insert themselves between engineers and the rest of the company.
I'm always interested in delivering value, but the fight necessary to actually do so has become stressful. It's no longer a collaboration, all my contributions must be filtered through the ego of the person speaking to decision-makers.
In fact, the only time I was actually satisfied with my work in the last 5 years (as opposed to my paycheck) was when I was acting as interim Product Manager for 9 months. Unsurprisingly, me and my team managed to deliver three projects that other teams tried and failed several times.
Most of that was accomplished by communicating with stakeholders and actually figuring out what they needed, rather than endlessly "trying to put my own spin" on it.
So yeah, I'm gonna keep delivering whatever is asked, getting the blame for bugs and not getting the credit for features. At least the pay is alright. I'm constantly searching for the place where I can actually fully contribute, though.
There are some people in my circles who have remained convinced that tariffs won’t actually amount to anything and that it’s all bluster.
It seems we’re now entering the “find out” stage, and it’s incredibly frustrating.
As a tinkerer who loves building things, this is heartbreaking stuff. I have projects in progress that may have to be put on hold.
I tend to order things as I need them, but it’s tempting to stockpile the basics. But I don’t think it will help much in the long run if this continues, and truly hope this madness will be seen for what it is and an appropriate backlash/correction will follow.
That is a very obvious thing for them to say though regardless of what they truly believe, because (a) it legitimizes removing the cap , making fundraising easier and (b) averts antitrust suspicions.
Using an LLM to do schoolwork is like taking a forklift to the gym.
If all we were interested in was moving the weights around, you’d be right to use a tool to help you. But we’re doing this work for the effect it will have on you. The reason a teacher asks you a question is not because they don’t know the answer.