Paul-Sebastian Manole

@fidexcode Have 9+2, don't work, too much neck strain. Tried 2, I miss Retina, plus sometimes feels not tall enough. Currently at 9, and loving it. Might sell 2 and try going back to the plain old 1, but Retina, and open up 9 once in a while when I need previews/docs to the side.

Which number is your current level of setup?

@Apple wtf are you doing with macOS? Tahoe is a huge step backwards in terms of design and UX. UIs on glass is a stupid idea. There's no contrast, everything is huge but still hard to read, padding is enormous... who gave this the green light? A 7yo?

@tannerlinsley @RyanCarniato @solid_js Can't wait for React to be rewritten from scratch!

.@RyanCarniato just showed me the future of async @solid_js and it's glorious. It's fundamentally changing what I thought possible for declarative UI and my positive outlook for frontend in general. No one is ready for this, but the beautiful thing is that no one needs to be.

The new Witcher is smug and snarky and he's always smiling at the corner of his mouth. There's no more sadness in his eyes. Just smug snarkiness. Plus everyone's gay now... 🤦‍♂️

@GergelyOrosz @martinfowler Classy!

Tomorrow - pod episode with @martinfowler coming

I've worked in "Agile" organizations for my entire 40+ year career, starting with my very first job. We didn't call it "Agile," of course, but we worked in small increments with plenty of customer feedback, leveraged CI/CD (though we didn't call it that, either), relied heavily on automated testing, paired on occasion (though not enough), etc. We had no ceremonies or roles or formal anything—we just worked (and communicated), and learned from our releases. We used those lessons to redefine what we were building. Interestingly, this work included hardware, which evolved along with everything else. Our architecture evolved incrementally as we learned. We also didn't have managers. There was somebody with the title, but they were completely hands-off. Our team was given a strategic objective and a delivery date, and the rest was up to us. Given that experience, I'm baffled by the focus on formal roles, ceremonies, & etc., having worked quite effectively without any of that. I haven't missed it. Every company I've worked with as a consultant that has emphasized those things (at first, at least) has been less effective than the less-formalized alternatives I've seen with my own eyes. Every. Single. One. This is an observation, not a theory. I'm also baffled by the "Scrum came first!" people who trot out dates in the late '90s or early '00s. The Manifesto was signed in 2001, but "Agile" existed for decades before that. The roots, in fact, go back to TPS and Deming's work in the 1970s. In any event, who cares? What matters is effectiveness. Effectively arguing "we're more Agile than you because we came first" seems ridiculous to me. So what's with all the frameworks and formalism? They all seem completely unnecessary.

@ChShersh I use eza instead of lsd. Any reason why the newer lsd tool would be better?

Upgrade your terminal experience with these CLI tools: 1. fzf 2. ripgrep 3. bat 4. lsd 5. starship 6. just 7. nushell 8. procs 9. k9s 10. difftastic 11. hyperfine

When will someone create a new language like #Kotlin but for the #Dotnet CLR, with the same easy interop story with the main language on that runtime? I'm tempted to say never, because F# is already amazing, but it just doesn't get the same adoption as Kotlin.

📚 Whenever I see useCallback, I wonder: why do we need it here? And a lot of the times, when I look deeper, I see that it actually doesn’t do anything. I think a lot of code-bases would be better of just not memoizing at all: tkdodo.eu/blog/the-usele…

Node excitement 😉 Congrats to @satanacchio on today's landmark Node 22.18 release. It is the first LTS release to ship unflagged TypeScript support 🎉 This means Node can run *.ts files. It pairs well with TypeScript's "erasableSyntaxOnly" flag 👍 Many folk contributed 🙏

@adhecson @evanyou Hardly a good reason and... Duh.

@evanyou Pulled back from Biome because I had one day that it ruined my code and failed to execute, once switched back to Prettier everything worked as expected

oxc formatter now at 60% compatibility with prettier for JS while being 3x faster than Biome

@ChShersh What must you know and be good at besides C++ in order to work for a hedge fund?

Huge announcement. I'm leaving Bloomberg as an OCaml Engineer. And.. I'm joining Bloomberg as a C++ Engineer. After using Functional Programming primarily for the last 10 years, it's time for me to switch gears. I moved to another team internally. I'll be working on low-latency real-time market data in C++. It's a big change for me. But I'm excited about a new challenge! AMA

I already believed this before agentic coding but now it’s undeniably clear to me. Any TypeScript engineering team not using Effect will be at a massive disadvantage. Basically the same story as using plain JS instead of TS.

@schickling @kitlangton Cool but not something you can't explain easily in one small sentence.

This is the most beautiful visualization of Effect I’ve ever seen (and heard 🔊). Take a look if you’d like to better understand how Effect works. Absolutely beautiful work @kitlangton!

@GergelyOrosz @czioutas This is an issue of expectations changing and them being implicit instead of explicit. You're both right.

yes but my point is that more and more companies will expect engineers to work in different stacks - when it's necessary sure there will be always places that are fantastic for specialists. just fewer and fewer! same way as if you're a backend dev today and only want to work with Java, or only with Ruby or only with {specific language} you will have fewer options than if you are open to working with a bunch of these or picking up whatever backend stack a company has

"Hiring pure backend engineer and expecting them to do non backend stuff IMO is wrong" Sigh. Any capable intern/new grad picks up whatever new technology is needed to get the job done. If you, as an *experienced* engineer, refuse to do so: you're less capable than an intern

@MichaelArnaldi @mattpocockuk Maybe the reason why ReScript didn't catch on is that it's so different from TypeScript but if you could create a superset of TypeScript and maintain separation and compatibility with it, by generating usable TS code, maybe TS+ can do what ReScript couldn't.

@MichaelArnaldi @mattpocockuk I think you should adopt a process similar to how ReScript works. It's a much more elegant solution and interoperability is perfect. You get clean JavaScript and TypeScript outputs you can commit to your repository even if you were to stop using ReScript.

Post Mortem on TS+, given requests by folks like @mattpocockuk : effect.website/blog/ts-plus-p…

@theo @mattpocockuk It's very simple. Effect<T, E, R> is just an extended Promise<T> (more or less). With that in mind you can get up to speed in a handful of weekends playing around with it.

@mattpocockuk How much do I have to pay you to just do it anyways? I need to learn effect so I can stop blocking my team lol

OK y'all I'm seriously considering taking a few months and building an Effect course. But I'm STILL not convinced the market's big enough. So sign up below if you're interested:

This is f-ing amazing engineering!

@MichaelArnaldi It's hard to be critical of something you're also trying hard to promote, but for some, like me, I'd rather know the cons as much as the pros, because only then I can truly appreciate it. There's no such thing as perfection.

By the way, just to let you know, our team is the most critical about Effect. There's many learnings that we went through and things we are far from being happy about. Constant improvement requires critical mindset.