Facts 👇🏼

Building AI-Ready Repositories with GitHub Copilot in Azure DevOps joshwgray.github.io/posts/bu… #githubcopilot #azuredevops #ai #developerproductivity #softwareengineering #devops

Vibe coding. The new doomscrolling

Just start.

ASP .NET Core Best Practices 💡 #dotnet Nice article providing guidelines from Microsoft for maximizing performance and reliability of ASP .NET Core apps. Which of these techniques are you using in your apps right now? Link in 2nd tweet below.

𝗕𝗼𝗼𝗸𝘀 𝗘𝘃𝗲𝗿𝘆 𝗦𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗘𝗻𝗴𝗶𝗻𝗲𝗲𝗿 𝗠𝘂𝘀𝘁 𝗥𝗲𝗮𝗱 𝗶𝗻 𝟮𝟬𝟮𝟱. You probably already noticed that I'm a big fan of reading. You can learn from knowledgeable people by working directly with them or reading what they have written. The first option is the best, yet it is often impossible. We have books written by people who were probably the best at this in the world at the time of writing. If we look at the software engineering world, there are many gems here, but I will recommend the best books per area of work. These books will help you not only to become good at specific technology but to become a great software engineer overall. 𝟭. 𝗚𝗲𝗻𝗲𝗿𝗮𝗹: 🔹 The Pragmatic Programmer by David Thomas and Andrew Hunt (amzn.to/3KzpVwj) 🔹 Code Complete: A Practical Handbook of Software Construction (amzn.to/3xbRF5O) 🔹 Modern Software Engineering by David Farley (amzn.to/3kqZaQ6) 🔹 Software Engineering at Google (abseil.io/resources/swe-book) 𝟮. 𝗖𝗼𝗱𝗶𝗻𝗴 𝗽𝗿𝗮𝗰𝘁𝗶𝗰𝗲𝘀: 🔹 Clean Code by Uncle Bob Martin (amzn.to/3KyVoyV) 🔹 Head First Design Patterns by Eric Freeman (amzn.to/3Kzq2YX) 🔹 Refactoring by Martin Fowler (amzn.to/3m8bAgo) 𝟯. 𝗗𝗮𝘁𝗮 𝘀𝘁𝗿𝘂𝗰𝘁𝘂𝗿𝗲𝘀 𝗮𝗻𝗱 𝗮𝗹𝗴𝗼𝗿𝗶𝘁𝗵𝗺𝘀: 🔹 Grokking Algorithms (amzn.to/3ksUw4e) 𝟰. 𝗗𝗮𝘁𝗮: 🔹 Learning SQL by Alan Beaulieu (Free - r-5.org/files/books/computer…) 𝟱. 𝗧𝗲𝘀𝘁𝗶𝗻𝗴: 🔹 Growing OO Software by Tests by Steve Freeman (amzn.to/3xRVaeB) 🔹 TDD by Example by Kent Beck (amzn.to/3EEHwiC) 🔹 Unit Testing Principles, Practices, and Patterns by Vladimir Khorikov (amzn.to/3ZBZYAJ) 🔹 The Art of Unit Testing by Roy Osherove (amzn.to/3kr7m2K) 𝟲. 𝗔𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗲: 🔹 Fundamentals Of Software Architecture by Mark Richards and Neil Ford (amzn.to/3xQ1EuD) 🔹 A Philosophy of Software Design by John Ousterhout (amzn.to/3IopUZm) 🔹 Clean Architecture by Uncle Bob Martin (amzn.to/3ERwsPw) 🔹 Domain-Driven Design Distilled by Vaughn Vernon (amzn.to/41slJoo) 🔹 Software Architecture the Hard Parts (amzn.to/3Zmg15r) 𝟳. 𝗗𝗶𝘀𝘁𝗿𝗶𝗯𝘂𝘁𝗲𝗱 𝘀𝘆𝘀𝘁𝗲𝗺𝘀: 🔹 Understanding Distributed Systems by Roberto Vitillo (amzn.to/3XZOFkG) 🔹 Designing Data-Intensive Applications by Martin Kleppman (amzn.to/41uO65o) 𝟴. 𝗗𝗲𝘃𝗢𝗽𝘀: 🔹 DevOps Handbook by Gene Kim (amzn.to/3m4iJ16) 🔹 Continuous Delivery by Jez Humble and David Farley (amzn.to/3ECoVUo) 🔹 Accelerate by Nicole Forsgren (amzn.to/3StOug6) 𝟵. 𝗠𝗮𝗰𝗵𝗶𝗻𝗲 𝗹𝗲𝗮𝗿𝗻𝗶𝗻𝗴: 🔹 The Hundred-Page Machine Learning Book (amzn.to/3Y1SIwN) 🔹 Designing Machine Learning Systems (amzn.to/4cw5FHM) #softwareengineering #programming #learning

My Favorite 10 Books for Software Developers General Advice 1 - The Pragmatic Programmer by Andrew Hunt and David Thomas 2 - Code Complete by Steve McConnell: Often considered a bible for software developers, this comprehensive book covers all aspects of software development, from design and coding to testing and maintenance. Coding 1 - Clean Code by Robert C. Martin 2 - Refactoring by Martin Fowler Software Architecture 1 - Designing Data-Intensive Applications by Martin Kleppmann 2 - System Design Interview (our own book :)) Design Patterns 1 - Design Patterns by Eric Gamma and Others 2 - Domain-Driven Design by Eric Evans Data Structures and Algorithms 1 - Introduction to Algorithms by Cormen, Leiserson, Rivest, and Stein 2 - Cracking the Coding Interview by Gayle Laakmann McDowell Over to you: What is your favorite book? -- Subscribe to our weekly newsletter to get a Free System Design PDF (158 pages): bit.ly/bbg-social

𝗧𝗵𝗲 𝗕𝗲𝘀𝘁 𝗘𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝗶𝗻𝗴 𝗕𝗹𝗼𝗴𝘀 𝗧𝗼 𝗙𝗼𝗹𝗹𝗼𝘄 𝗶𝗻 𝟮𝟬𝟮𝟱. Here is the list of software engineering blogs I follow regularly to upgrade my engineering skills: 1. LinkedIn Engineering: engineering.linkedin.com/ 2. Engineering at Meta: engineering.fb.com/ 3. Dropbox Tech Blog: dropbox.tech/ 4. Spotify Engineering: engineering.atspotify.com/ 5. Netflix Tech Blog: netflixtechblog.com/ 6. GitHub Engineering: github.blog/engineering/ 7. Stripe Blog: stripe.com/blog 8. Uber Engineering Blog: uber.com/en-RS/blog/engineer… 9. Slack Engineering Blog: slack.engineering/ 10. Engineering@Microsoft: devblogs.microsoft.com/engin… 11. Airbnb Tech Blog: medium.com/airbnb-engineerin… 12. AWS Architecture: aws.amazon.com/blogs/archite… 13. Discord Blog: discord.com/blog 14. Figma Engineering: figma.com/blog/engineering/ 15. Instagram Engineering: instagram-engineering.com/ 16. Pinterest Engineering: medium.com/pinterest-enginee… 17. StackOverflow Engineering: stackoverflow.blog/engineeri… 18. Twitter Blog: blog.x.com/engineering/en_us 19. Notion Tools: notion.com/blog/topic/tech 20. Discord Blog: discord.com/blog What should be added to this list?

Using .NET Keyed Services with Strategy pattern #dotnet I posted a strategy pattern example yesterday and someone on LinkedIn suggested using Keyed Services in .NET could simplify things. Hadn't really considered this, but using Keyed Services seems to negate the need for the context class we see in traditional implementations of the strategy pattern. Two examples below ⬇️ One using Enums for strong typing and the other using plain strings for simplicity. What do you think?

Visiting Cape Town from Ireland for the Christmas/New Year holidays. Thought my euros would go far here. They didn’t. Cannot believe how expensive this place has gotten in less than 2yrs.

Today we got banned by GitHub. The rate of new repos and commits created by our users was putting too much strain on their infra. A single AI codegen startup generating so much code that it makes Github struggle is an early indication of how much software that AI will produce from here on out.

Want to level up as a software engineer? My 4 predictions for 2025. 1. Become best friends with AI tools. Not just using them but also understanding their strengths and limitations. Spend time learning prompt engineering and when NOT to use AI. Cursor Claude Sonnet are my go-to AI coding tools. GitHub Copilot is catching up quickly (keep an eye on it). 2. Master the art of learning in public. Share your debugging journeys, document your failures, and build in the open. The best engineers I know aren't just building - they're bringing others along through detailed technical blogs and thoughtful code reviews. Almost no one is doing this, so it's an easy way to stand out. 3. Develop your systems thinking muscle. Modern engineering isn't about individual services anymore. Whether you're dealing with distributed systems or simple APIs, understanding how everything connects (and fails!) is crucial. Observability and monitoring will be even more important. 4. Prioritize sustainable development (not what you think). This means writing maintainable code, yes, but also maintaining YOUR sustainability. Regular breaks, deep work sessions, and knowing when to step back are crucial engineering skills. What would you add to this list? P.S. Stay awesome!

A great opportunity 👇 One of Irish cycling’s top teams is looking for new riders for 2025 stickybottle.com/latest-news…

Somebody over at CrowdStrike is having a very stressful day

𝗦𝘂𝗰𝗰𝗲𝘀𝘀 𝗶𝘀 𝘄𝗼𝗿𝗸𝗲𝗱 𝗼𝗻! Which quote resonates for you? In any case, to succeed is to want, try, fail, and try again to succeed finally! You need a winning mindset! I wish you a great week ahead 👋! #leadership #personaldevelopment #success #careers #techworldwithmilan

Accurate!

1/2 masters thesis help needed: If you’ve completed a Cycling Ireland coaching course and are currently coaching at the grassroots level, I’d love to connect with you. Unexpectedly, some participants have had to withdraw

True story!

Registration for #TheDES24 now open. Closing Friday 22nd March 9pm. Early entry would be appreciated by our organising committee. 👇eventmaster.ie/event/vvercPo…