Dan Patrascu
@danpdc
📽️YouTube: https://www.youtube.com/c/Codewrinkles 📖Blog: https://codewrinkles.com/ 📧Newsletter: https://codewrinkles.eo.page/newsletter
The past few months I've been talking to conferences, user groups and universities across 3 different countries. It's always a great pleasure for me to participate in such events and I'm always happy to talk towhoever wants to listen. My last experience at #PeakIT06 was a blast!…




I didn't expect that. Got almost 100 new members on the Codewrinkles Discord server after I made it totally free and don't bind membership to a YouTube membership. I get less money, but a more vibrant community. I'll take it!
There are 3 things you should consider from the planning / design phase of a new project: 1. Code quality 2. Consistent standards across the team 3. Security There are plenty of tools that can help you achieve this. Some of them are even free.
Agile and what it has become in >90% of the orgs that do product engineering is just "busy work". Instead of delivering value faster, it delivers value slower and at a notably higher cost.
I actually didn't write too many lines of code this evening, but I managed to create for myself a project setup that guards for code quality and security in a pretty neat way. Trying to stick to things that are free, I have managed to: 1. Set up coding standards via…
Like this
Manage NuGet packages for an entire solution and the option to consolidate packge versions across projects is one of the best things that happened to Visul Studio recently!
Manage NuGet packages for an entire solution and the option to consolidate packge versions across projects is one of the best things that happened to Visul Studio recently!
A generalization like this shows a deficiency in understanding that EU is a bunch of totally different cultures. But then again, I've seen this so often: "Fact: There's a typo in a config file. Fix: escalate this to streamline the delivery and eradicate possible bottlenecks"
when hiring you should highly scrutinize: - faang employees. - europeans. none of them seem to want to do any real work for some reason, only fake work.
One of the apps at my new work is around 20 years old. Plain old web forms -> data access -> db. Where virtually all business logic in SPs. No useless abstractions, no mappers. I'm not a fan of all logic in the db, but I think it's better than a lot of the clean approaches
Architecting and building a Windows installer type of app is not easy. So many things to think about like considering what to do if any step goes wrong, verifying files, checking .ini configs, cleaning up and so on.
And btw, I really like #windows and #msteams. Now go ahead and say I'm a bad developer. You're right!
Note to self: don't play blitz chess in the evening after a day with a 2 hours intense workout started at 6 AM following by an 8-hours work day and a tech presentation after work
Starting over at a new company in your 40s can be very overwhelming as your brain gets continuously bombarded with new stuff for 8 hrs a day. But it's also very exciting
I don't think this is a bad advice. It's simply different and what it might seem to be fairly old school, but still valid. Moving "data access to the database" doesn't mean moving the BLL to the db. You can definitely version your db schema changes even without EF. Most of the…
It's bad advice. I've got such a comment under my post with an optimized SQL query in EF 9. When you should avoid writing your BLL in the SQL database: - you want to have better version control of changes - you want to have code that is easier to test, maintain, and debug 1/7
Today I have started an exciting new journey by joining @TheAccessGroup as a Divisional Software Architect. Together with tens of bright engineers we'll take care of the entire app ecosystem for legal businesses mostly around the United Kingdom. I love technical challenges and…
Posting on @X that you'll stop posting on X. LMAO 🤣
Why the Guardian is no longer posting on X theguardian.com/media/2024/nov…
One of the most dangerous mindsets we live nowadays is that every product needs to be "infused with AI". Mostly wrappers around LLMs. If we don't understand that there's just a small subset of problems that can be solved by LLMs, the AI bubble will share the web3 destiny
I think the buzz around .NET Aspire shows exactly what the problem is with online content in general. Most of the posts are around the Dashboard. Which is nice and cool, but it's literally the least important thing about .NET Aspire.
Change is the only constant in life, yet we continously try to fight it. Still, there are moments when getting out of the comfort zone and embracing change can have overwhelming positive benefits! It's in this context that I have decided to embrace change and embark on a journey…