Ray

Developer / Jogger

[Mitchell Hashimoto @mitchellh]

The "whiteboard defense:" I should be able to pull you aside at any moment and ask you to explain any customer-facing system you've shipped. You should be able to clearly explain how it works and defend the decisions you made. This is my benchmark for responsible AI usage.

I don't expect line-level familiarity with the code. I don't care if you remember the exact function name or implementation detail. You may not even know it. I don't care.

But if I ask "why did you do X instead of Y?", "what happens if this actor behaves maliciously?", "what data structure did you use here and why?", or "where does this fail?" you should be able to answer confidently.

For PoCs, demos, experiments, whatever: I don't care. Generate 100% of it and understand none of it. Speed over quality every time in those specific scenarios.

But if you're shipping customer-facing work, you can't be shipping things you don't understand at a high level.

[Mitchell Hashimoto @mitchellh]

Guess which one is Rust btw. 🤣

(The point is the language isn't a free lunch for performance. Rust could be just as small as any other here. It isn't a given. Fundamentals and system design trump everything else. Language wars are stupid as hell.)

[Richard Feldman @rtfeldman]

Since the @bunjavascript folks recently wrote about their experience moving from Zig to Rust, it seemed like a good time to write about our experience rewriting @roc_lang from Rust to Zig!

https://t.co/JkPboqnGTn

[kitze 🛠️ tinkerer.club @thekitze]

iykyk

[Conner Cowling @conner_xyz]

More than microservices vs. monoliths, the underlying anti pattern here is the Death Star project.

It’s the arrogance of believing you’ll single handedly redesign the whole thing better than the evolutionary process that created the original, that the landscape is static, and that you’ll have all the time and money needed to do a complete overhaul.

In other words, a recipe for failure in form of faulty assumptions, partially completed reforms, delayed schedules, and budget overruns.

If you end up here, pray execs see it for what it is and don’t end up in sunk cost fallacy land.

What’s the answer then? Test and iterate.

Whether its architecture or org changes, have a destination in mind, make changes in degrees, respond to what happens next.

It doesn’t matter what the architecture is. Focus on outcomes, acting and adapting.

[Ray @cloudy9101]

if you wish to make an apple pie from scratch, you must first invent the universe.

[DHH @dhh]

Rails 8 Beta 1: No PaaS Required has been released! Everything you need to go from HELLO WORLD to production on any Linux server, whether Cloud VM or a Pii in your closet, is included. https://t.co/1PLKRoLZBz

[Namya @ Supafast @namyakhann]

Reminder to myself and whoever needs it: Stick to the plan!

[Ray @cloudy9101]

@housecor Just use fetch, please. More code is not always bad.

[fofr @fofrAI]

Me when my code isn't working

[Ray @cloudy9101]

OK, now more people know OpenAI and ChatGPT 4o. Is this what they do to gain more users?

[Bobby Allyn @BobbyAllyn]

Statement from Scarlett Johansson on the OpenAI situation. Wow:

[Ray @cloudy9101]

This is a test @cloudy9101

[Ray @cloudy9101]

Hey friend, would you be willing to share some insights about the latest GPT-4o language model?

[Ray @cloudy9101]

This is a test

[Ray @cloudy9101]

👏

[Neovim, e/plugins @Neovim]

here, have a text editor: Nvim 0.10

https://t.co/ljPPOB2lfZ

https://t.co/5d3Po5bKsd

[Remix 💿 @remix_run]

We have an announcement

https://t.co/WBG18EsLvG

[Ray @cloudy9101]

Still no gpt4o in my account 😔

[Ray @cloudy9101]

@PeterSaulitis YES. Every MVP is just built with
Pages - serve static files
Workers - serve dynamic content
D1 - Database
KV - KeyValue store
R2 - Object store
(Workers AI if AI-based)
The amazing part is all these are simple to use.

[Ray @cloudy9101]

@nilansaha Good call out. Focus on goals instead of tasks.

[CJ (Coding Garden) @CodingGarden]

I'm a big fan of self documenting code.