Dario Kondratiuk

In case you missed the news, My book UI Testing with Puppeteer is available on Amazon! I think it's a great introduction not only to Puppeteer but also to browser automation! 🙂 amazon.com/Testing-Puppet…

@mothsq @grok explain to me why some countries use whatapp instead of messages but say it like im 5

can somebody explain to me why some countries use whatapp instead of messages but say it like im 5

@yenkel yup. Free as "OSS as Marketing, please buy my cloud services"

@hardkoded free as in beer but not attachment free?

This is why we need to stop calling OSS to products maintained by corporations. That popular "open source" you use that it's free, depends on a budget of some manager at a big corporation.

@ybhrdwj Some projects gets people laid off just because they live in the “wrong” country. Others relies on sales from their docs. Others are bought and manipulated to do stuff that only serves one company. This is not open source. OPEN SOURCE IS BROKEN

Tailwind lays of 75% of their team. the reason is so ironic: > their css framework became extremely popular w AI coding agents, 75m downloads/mo > that meant nobody would visit their docs where they promoted paid offerings > resulting in 40% drop in traffic & 80% revenue loss

You know it's a lie when they begin with " Yes, and don't ask again for similar commands"

@czoob3 Look at those faces. So happy. So full of life.

9:15 pm Monday night. Not a single Eng has left yet. The only thing to do in life is build.

Well, that's pretty much like doing open-source.

@theonecid Edge

Which browser is the best in 2025?

Writing a book be like

@AntonMartyniuk 41. Never write long lists of stuff 🤣

12 years as a .NET developer – in 60 seconds I have learned many lessons. Some of them were painful, others were priceless. Here are the 40 most important takeaways 👇 0. The best code is the one you don't write 1. You're not paid to write code - you're paid to solve problems 2. Everything is a trade-off. There's no "best" tool 3. Write code that other developers will enjoy working with 4. Write meaningful commit messages 5. First make it work, then make it pretty 6. Ship early, iterate often 7. Estimations are never true 8. Refactor continuously and incrementally 9. Code reviews improve more than just quality — they improve teams 10. Never trust user input. 11. Log precisely, not excessively. 12. Automate everything that can be automated 13. Complexity kills project, don't over-engineer 14. Fix root causes, not symptoms 15. Measure first, optimize second 16. Minimize coupling, maximize cohesion 17. Keep third-party dependencies minimal and well-managed 18. Never hard-code sensitive information 19. Errors should fail loudly and immediately 20. Choose clarity over cleverness 21. Choose descriptive naming over explanatory comments 22. Favor composition over inheritance 23. Complexity doesn't scale; simplicity does 24. Respect the principle of least surprise 25. Remove unused code without hesitation 26. Think and code in small, testable units 27. Be consistent with your coding standards 28. Abstraction should hide complexity, not create it 29. Favor explicit over implicit 30. Every line of code should justify its existence 31. Always strive to understand the business behind the code 32. Keep Pull Requests small and manageable 33. Invest in CI/CD right from the start 34. Design APIs that are easy to use correctly and hard to misuse 35. Document why, not just what 36. Forget about "it works on my machine" 37. Be aware of technical debt; repay it incrementally 38. Balance YAGNI ("You Aren’t Gonna Need It") with thoughtful design 39. Ask for help when you're stuck 40. Never stop learning and questioning your assumptions —— 👉 Join 𝟭𝟱,𝟬𝟬𝟬+ people in the best .NET and Software Architecture Newsletter. Weekly best practices, real-world examples, and pro tips to craft better software today! Link in the featured section of my profile. 𝗕𝗼𝗻𝘂𝘀: every subscriber gets a PDF with 650+ exclusive resources for mastering C#, .NET, ASP .NET Core, EF Core, and Microservices. —— ♻️ Repost to help other developers learn these 40 lessons in minutes, not years ➕ Follow me ( @AntonMartyniuk ) to improve your .NET Skills

@kristijan_kralj @kellabyte Those layers are important in case you need to switch form SQL to JSON files sorted in your file system.

The hidden cost of enterprise .NET architecture: Debugging hell. I've spent 13+ years in .NET codebases, and I keep seeing the same pattern: Teams build fortress-level abstractions for problems they don't have. IUserService calls IUserRepository. IUserRepository wraps IUserDataAccess. IUserDataAccess calls IUserQueryBuilder. IUserQueryBuilder finally hits the database. To change one validation rule, you step through 5 layers. To fix a bug, you open 7 files. The justification is always the same: "What if we need to swap out Entity Framework?" "What if we switch databases?" "What if we need multiple implementations?" What if this, what if that. The reality: Those "what ifs" don't come to life in 99% of cases. I've seen exactly zero projects swap their ORM. But I've seen dozens of developers waste hours navigating abstraction mazes. New developers are confused about where to put a new piece of functionality. Senior developers are debugging through the code that has more layers than a wedding cake. The end result? You spend more time navigating than building. Look, good abstractions hide complexity. Bad abstractions create it. Most enterprise .NET apps have way too much of the second kind.

@MicrosoftEdge why can't Copilot read this news website infobae.com?

THIS IS NOT OPEN SOURCE

If your PR description is a link to a private ticket system, your project is not an open-source project; it's corporate marketing.

What????? @MicrosoftEdge can scrape data from a website!!!

@TheAppleDesign Easy bro, I just need to turn off the wifi.

Liquid Glass is not just another 2D UI.. It’s a 3D UI which processes all the effects in real time Accept it or not but Liquid Glass is the PEAK OF SOFTWARE DESIGN

Copilot, please fix.

@nick_cloudops Thank you!

@hardkoded Congrats 🥳🥳

I know that I say the same thing every year. But it feels the same every year! You go from denial, sadness, and acceptance until you finally receive the email you've been waiting for. I'm thrilled to have been awarded the Microsoft MVP award for the 6th consecutive year! #mvpbuzz

@jrusansky Thank you!!!

@hardkoded Congrats man! 🎉🎉