That's very interesting, although I'm still curious about the training resource usage -- not "only" inference. I wonder what is the relative importance of training (i.e., what percentage of the resource usage was in training vs. inference)
Readit Newsvitorbaptistaa commented on In a first, Google has released data on how much energy an AI prompt uses technologyreview.com/2025... · Posted by u/jeffbee
vitorbaptistaa commented on All-In on Omarchy at 37signals world.hey.com/dhh/all-in-... · Posted by u/dotcoma
I love dhh and I applaud his manic obsession with Linux over the 18 months or so that I've seen on my twitter feed. I still don't exactly understand what the purpose of all of this is.
I'm sure it is very configurable, but every visual I've seen of this thing looks awful and not something I'd want to look at while working. But I understand we all have different tastes.
But even in the blog post I'm struggling with 'why?' here. Am I to understand the primary benefits here are improved battery life and increased developer productivity by tests running faster? Is that it?
I travel an inordinate amount and have never found a Macbook's battery life to be insufficient. I struggle to even remember the last time I've used my computer long enough to drain the batter and not be near a power outlet. I work from ski lodges, planes, my car. This has never been a problem for me. Not once. This just feels like a really bad metric to optimize for given a typical developers' schedule and work arrangement.
> On the flip side, we'll get a massive boost in productivity from being able to run our Ruby on Rails test suites locally much faster.
Is this not just a Ruby issue? I don't know what's basecamp or HEYs codebase looks like on the inside, but they don't feel like projects whose tests suites should require a completely different OS or hardware arrangement. I haven't used Ruby in a decade but I do recall it being frustratingly slow. This seemed to be an understood and accepted reality amongst teams that adopt it.
Anyway, I feel like a better 'why you should do this' in order, especially if it is being mandated amongst developers in a company.
From what I understood, the initial motivation wasn't technical, but related to Apple's practices around a closed app store and the 30% tax on every purchase. He explained it both on Lex Fridman's podcast at [1] and a bit on [2].
[1] https://www.youtube.com/watch?v=mzDi8u3WMj0 [2] https://world.hey.com/dhh/living-with-linux-and-android-afte...
vitorbaptistaa commented on All-In on Omarchy at 37signals world.hey.com/dhh/all-in-... · Posted by u/dotcoma
This has been one of the most surprising developments of late, given DHH's and Rails devs historical preferences for Apple products. I'd love to see some stats on the impact of this change.
After many years using Ubuntu, I migrated to Omarchy this weekend (Arch Linux + Hyperlnd, a tiling window-manager). Looking great so far!
vitorbaptistaa commented on Developing with Kiro: Amazon's New Agentic IDE yehudacohen.substack.com/... · Posted by u/cebert
From the article:
> What I found interesting is how it forced me to think differently about the development process itself. Instead of jumping straight into code, I found myself spending more time articulating what I actually wanted to build and high level software architectural choices.
This is what I already do with Claude Code. Case in point, I spent 2.5 hours yesterday planning a new feature - first working with an agent to build out the plan, then 4 cycles of having that agent spit out a prompt for another agent to critique the plan and integrate the feedback.
In the end, once I got a clean bill of health on the plan from the “crusty-senior-architect” agent, I had Claude build it - took 12 minutes.
Two passes of the senior-architect and crusty-senior-architect debating how good the code quality was / fixing a few minor issues and the exercise was complete. The new feature worked flawlessly. It took a shade over 3 hours to implement what would have taken me 2 days by myself.
I have been doing this workflow a while, but Claude Code released Agents yesterday (/agents) and I highly recommend them. You can define an agent on the basis of another agent, so crusty-architect is a clone of my senior-architect but it’s never happy unless code was super simple, maintainable, and uses well established patterns. The debates between the two remind me of sitting in conf rooms hashing an issue out with a good team.
Would you mind sharing the prompts you use for your subagents? It sounds very interesting!
Visa and MasterCard are shaking in their boots and will scratch and bite on their way down to kill anything like this in the US.
This has already started with Trump's tariffs: https://valorinternational.globo.com/foreign-affairs/news/20...
> While the system is not named directly, a document from the Office of the United States Trade Representative (USTR) says that “Brazil also appears to engage in a number of unfair practices with respect to electronic payment services, including but not limited to advantaging its government-developed electronic payment services.”
I'd be surprised if there aren't big tech/credit card companies lobbying behind this.
>It is just better in my experience.
>You just scan a QR code and pay.
Tap to pay (ie. NFC) with credit cards is as convenient and arguably more convenient than a QR code solution. At the very least you don't have to worry about aiming at the QR code and waiting for it to scan/focus, which is especially important if you're using it on transit systems.
Pix already has tap to pay [1]. However it's still a recent adition (a few months), so most card machines still don't support it (AFAIK).
Once this is widespread, then the only reasons to use credit will be cashback/points or paying in credit.
[1] https://www.gov.br/secom/pt-br/assuntos/noticias/2025/02/pix...
Yeah, the dissonance of day to day stresses and societal issues with mass extinction is hard to deal with. I’m currently putting together a pile of a few books that claim to have pragmatic but optimistic/hopeful views of where we go from here.
Any good suggestions so far? The best I read was Not The End of The World by Hannah Ritchie from Our World in Data.
And consider these are 800k galaxies mapped in the subtending angle of three moons in the sky...
If Claude is correct, these 0.54 square degrees represent 0.0013% of the full 41,253 square degrees of the sky (4*pi steradians).
Deleted Comment
vitorbaptistaa commented on Ask HN: What is the simplest data orchestration tool you've worked with? · Posted by u/chordol
My experience entails:
* Luigi -- extensive usage (4y+)
* Makefiles -- (15y+)
* GitHub Actions -- (4y+)
* Airflow -- little usage (<6 months)
* Dagster -- very little, just trying it out
* Prefect -- just followed tutorial
Although it lacks a lot of the monitoring and advanced web ui other platforms have (maybe because of it), Luigi is the simplest to reason about IMHO.
For a new project that will require complex orchestrations, I'd probably go with Dagster or Prefect nowadays. Dagster seems more complex and more powerful with its data lineage functionality, but I have very little experience with either tool.
If it's a simple project, a mix of Makefiles + GH Actions can work well.