Sabitlenmiş Tweet
Having semantic overloading in your codebase can lead to frequent micro context switches.
English
Marian Posăceanu
6.6K posts
Marian Posăceanu
@dakull
I'm a latte fuelled, mostly analogue, Rubyist.
Constanța, Romania Katılım Ekim 2008
839 Takip Edilen584 Takipçiler
Marian Posăceanu retweetledi
Human in the loop viewed as "we have exhausted most of written content, we need live humans to train the next model"
English
We should strive to keep the sloppynes gradient as low as possible in our codebases.
English
Marian Posăceanu retweetledi
@dhh CPUs nowadays are as powerful in ST as a quad-core Intel of the *Lake era so we can run megabytes or JS in a chromium tab ...
English
The web was amazing prior to the reactification of everything 😄. Hotwire's Turbo framework is based on Chris Wanstrath's original Pjax concept (that powered GitHub in those early years). This kind of speed is still possible!
Sam Lambert@samlambert
GitHub's performance in 2013. The web used to be so fast.
English
@oprearocks Yes, yes it does need a full clean-up - a pinch of izopropilic alcohol on a microfiber can clean up the oil on the keyboard.
English
woo hoo
Mitchell Hashimoto@mitchellh
Ghostty 1.3 is now out! Scrollback search, native scrollbars, click-to-move cursor, rich clipboard copy, AppleScript, split drag/drop, Unicode 17 and international text improvements, massive performance improvements, and hundreds more changes. ghostty.org/docs/install/r…
English
@davepl1968 I did not add anything HEDT gist.github.com/marianposacean… this is impressive - I am curios about the thermals though.
English
Marian Posăceanu retweetledi
In the past hour, I've been linked to two independent studies that show Ruby is among the best languages for AI coding tools, both in token count and speed of implementation. In both cases it was better than Python or JavaScript by a comfortable margin.
English
Update: ok so Apple is playing massive marketing tricks to make it sound better than it is. Renaming Perfomance cores to super cores. M5 Max is only 15% faster than M4 Max.
It’s not nearly as good as it sounds..
English
HOLY SMOKES!
Apple ditched efficiency cores! Now using 6 Super cores and 12 Perfomance cores. WHAT!!!
Over 30% improvement in multi-core CPU Perfomance was NOT expected..
Vadim Yuryev@VadimYuryev
Took Apple long enough lol! Now we can wait for M5 Ultra in June!
English
@kayintveen @dhh Indeed - the more code is being generated the more this compounds too: what code should not have existed in the first place.
Without LLMs part of that limit was purely human, but now it's gone.
English
@jasonfried Please, by all means continue with these posts - love them.
English
Rolex Milgauss. 1958 (lightning)... 1978 (red arrow tip)... 2021 (orange lightning).
Once again, the original is the best.
(photos via tropicalwatch.com)
English
English
LOC is a very useful metric in the LLMs "era" as they can produce orders of magnitude more LOC than humans i.e. it becomes an obvious smell since our mushy brains do not have the capacity to grok them.
Lateral: great read from @nateberkopec nateberkopec.com/blog/37signals…
English
Anthropic: Our AI agents coded the C compiler 💪🏼
The compiler:
English
@GergelyOrosz @rockatanescu Marketing aside, deep down - we all knew this would happen at some point. Killing the free tier, barely any real improvements and now this.
As a Ruby dev - Heroku was always special - I still remember their initial design, naming and how easy it was to deploy a Ruby app ...
English
@rockatanescu It’s exactly why it doesn’t make sense doing so
Salesforce just opting to pass on an explosion of PaaS of apps is so strange to see
English
Translation of this nonsense corporate talk:
“We will be killing Heroku
Not today and not tomorrow
But don’t say we didn’t warn you
PS: I’m just a marketing guy here and they told me to write something that legal would approve so here you go:”
Heroku@heroku
Heroku is transitioning to a sustaining engineering model focused on stability, security, reliability, and support. Heroku remains an actively supported, production-ready platform, with an emphasis on maintaining quality and operational excellence rather than introducing new features. We know changes like this can raise questions, and we want to be clear about what this means for customers. There is no change for customers using Heroku today. Customers who pay via credit card in the Heroku dashboard—both existing and new—can continue to use Heroku with no changes to pricing, billing, service, or day-to-day usage. Core platform functionality, including applications, pipelines, teams, and add-ons, is unaffected, and customers can continue to rely on Heroku for their production, business-critical workloads. Enterprise Account contracts will no longer be offered to new customers. Existing Enterprise subscriptions and support contracts will continue to be fully honored and may renew as usual. Why this change We’re focusing our product and engineering investments on areas where we can deliver the greatest long-term customer value, including helping organizations build and deploy enterprise-grade AI in a secure and trusted way.
English
Pro SQL tip:
Stop writing LEFT JOINs and start writing the *right* JOINs 🥁
English
@theo There's Asahi which runs on the MacBook Pro but you need to revert to an M1 Pro CPU or M3 Pro when the GPU drivers are done. Then again the M1 Pro is far from being a slow computer.
English
I am way happier with Linux than I expected to be. Almost all the issues I have are with hardware quality.
Mushy keyboard, flimsy screen with washed out colors, awful speakers, don't get me started on the trackpad...
English