"How can we automate moving stories from current to next sprint in Azure DevOps?"
You're trying to automate away pain that is a symptom of a problem with your process.
#AzureDevOps#DevOps#scrum
The underlying problem is that you're trying to stuff too much into a sprint. If you're close to accurate, then you should be over half the time and under half the time, and only by a little bit, so there shouldn't be enough work to require automation.
Mar 22, 2023 • 4 tweets • 1 min read
Clean architecture aka ports and adapters is simply an approach to building systems that follow DIP. That is, depend on abstractions not implementations, and make sure those abstractions don’t depend on details. #dotnet#cleanarchitecture
It doesn’t make exceptions for different kinds of implementations. It doesn’t exclude web services or email sending or file system access. Why would it be inconsistent about persistence or ORM usage?
Mar 29, 2022 • 14 tweets • 3 min read
Everybody in the software development industry understands that learning is important if you wish to stay relevant over the long term.
So, it helps to have some kind of strategy or process for learning. You have one, even if it's just a random, default one. The fact that you're reading this means you likely incorporate twitter as part of your learning strategy.
Mar 28, 2022 • 4 tweets • 1 min read
If every software developer graduated college with a bachelor’s degree that included all of the things we wish it did, it would be at least an 8 year degree.
Most 4-year degrees already are chock full of required courses leaving little room for electives (and often only a handful of courses on one’s MAJOR).
Oct 13, 2021 • 4 tweets • 1 min read
A while ago before package managers and in dotnet land, nuget, many devs would put the dependencies their project needed to build in a “lib” folder.
Then package managers took off and became stable and trustworthy (for the most part), and distributed source control made it even more important to keep checked in code small.
Jul 21, 2020 • 13 tweets • 3 min read
I'm working on a new workshop that will guide students through an array of different data access approaches for OO languages (.NET/C# specifically). I like to start such topics off with principles that apply to the space. Here's what I have so far - am I missing anything obvious?
These are "data access principles" which when I searched I didn't find any handy lists. I'll probably write up a blog post on the topic soon.
Mar 7, 2020 • 20 tweets • 4 min read
So you find that now you're suddenly going to #WorkFromHome? Here are some tips I've picked up over the years, on how to be productive and also participate in teams without being in the same room or face-to-face. (Thread)
It helps if your team is remote-first. If everyone just got sent home because of COVID-19 concerns, then the upside is that you're not the lone remote worker on a team who are otherwise all together. So you're not going to miss out on hallway conversations, etc.
Oct 25, 2018 • 7 tweets • 3 min read
When you have two systems that need to communicate, the default for 90+% of companies is to use a shared database. (thread) #dev#programming#architecture#softwarearchitecture
Most never move off of this model, but it has disadvantages that go along with the ease of sharing data. Applications lack encapsulation and cannot adapt their data designs to suit their unique requirements.
