Rafael Milewski

@freekmurze This guy @natebjones" target="_blank" rel="nofollow noopener">youtube.com/@natebjones

What are the best YouTube channels and newsletters for AI development? I like watching/reading people who: ✅ can explain concepts in a clear, calm, friendly way. ✅ are enthusiastic, but also honest/critical at the same time ✅ actually use all of it in their own stuff Also, I’m an adult and like to be treated as such, so: ❌ no thumbnails with funny faces. ❌ enthusiasm is fine, but no hype-hype-hype, over-energetic stuff ❌ no clickbaity stuff like “15 tips that will TOTALLY blow your mind.” Such content has an audience too, I guess, but maybe I'm too old to be part of it 🙂

One shot left. What should I build?

@enunomaduro Nuno, you speak português, you know what pao sounds like.. Yet you choose to do this.. Real life troll 😂

all my projects, starter kits, and packages now use pao in just one week: close to 400 github stars, almost 100,000 downloads start saving tokens today: composer require nunomaduro/pao --dev

@taylorotwell I’m all for it, however, I see a major disadvantage in using attributes for newcomers. The way I learned what was possible in Laravel was mostly by pressing Ctrl + Space and seeing what could be set or overridden. With attributes, I’ll have none of that...

Laravel was written before PHP had attributes, so we used properties to define configuration on things. After attributes were introduced, we've accumulated a few attributes that can be used to configure behavior. However, the mix of attributes and properties makes things feel inconsistent. Sometimes you use an attribute, sometimes you use a property. 🤮 For Laravel 13, I've been going through the framework and creating attributes where possible, while still allowing fallback to properties so there are zero breaking changes. 💪 github.com/laravel/framew…

Mother Earth will soon become a motherboard...

@akramcodez github.com/milewski

Drop your GitHub profile, I'll give my opinion on it.

@nalinrajput23 If hype and quality was 100% I would say Rust

Guess the programming language

Mind your .unwrap()!

@k_flowstate The rubber gets sticky/mushy after a while

I have never heard a bad review about this mouse

@DataChaz Lost the opportunity to call it jsoff

If you’re still sending raw JSON into your LLMs, you’re burning tokens, latency, and budget! Try TOON (Token-Oriented Object Notation). Clear like YAML, compact like CSV: • 30–60% fewer tokens • Up to 50% lower costs • Shines for tabular data. Free and Open source 🧵↓

@ocodista Esses aqui: github.com/milewski

Qual repositório de código aberto é referência em qualidade de código?

@github @github

@github Could you please fix this issue where I'm receiving undismissable notifications from repositories I've never participated in? It's been annoying me for days....

ooooooo rusty burn

@jdegoes Ok(())

Btw we hire Rust engineers and we're not insane. Just saying'

@rqobela In Rust we trust

Which language do you trust in production?

@krishdotdev Both are good on their own ways, Go is good for web apps and developer tools, And Rust is best for everything that Go is good at plus everything else.

Let's end this debate ! Which side are you on and why ?

@PovilasKorop Would you rather have your application catastrophically throwing an error to the user face when a log fails to write? Or ignore the error and fall back to another way to log that won't disrupt the request?

Please explain smth to me. I recently saw this code in some Laravel package internals. Repeating try-catch statements, catching regular Exception, with nothing useful in the "catch" block. With comments "silence is golden". (written by AI? not sure) But... WHY? Is it worth creating try-catch when you don't do ANYTHING in the catch? If some exception happens, then Laravel should handle it, or you override that handling with custom exceptions. I even created a full course (link in the reply) to explain WHEN to use exceptions and what useful can you do then (logging, returning different results, etc). But cases like this one kinda trigger me. Do I misunderstand something, or these snippets would be cleaner WITHOUT try-catch at all?

@JLarky No, but have you seen dagger.io?

would you use something like this instead of YAML for github actions?

@Adityapandeydev Install ComfyUi

thinking what should i install on this beast

For those who work with #ComfyUI I started a project that allows writing custom node in #Rust github.com/milewski/comfy…