What is Null? Null is an adjective that means “without value”. It is the absence of knowledge. It is “I dunno”. Null sounds like a very computer-y thing, but it’s something we encounter in everyday life away from our computers, we just don’t realize it. For example, let’s say someone tells us “I have a… Continue reading What is Null and what are null contexts in C# 8.0?
Most developer blogs are in the structure of learn a thing, write a thing. This is where we find something we need to do, we learn how to do it, then we document what we did so that others can follow it. This feels very helpful with something is obscure or not documented well. However… Continue reading Writing Java in VSCode and Understanding What Pressing F5 Does
As high performing development teams we need to have individuals on our teams with high technical knowledge and individuals with high domain knowledge as well as many other factors to keep our teams performing well. However the most important thing we all need for our teams to perform their best is psychological safety. What Is Psychological… Continue reading Encouraging and Maintaining Psychological Safety in Software Development Teams
“Hey Framework! Any time this API endpoint is called and we create an object that is a SomeController that needs an IDoThingsService, create a brand new DoThingsThisWayService and use that. When the SomeController object gets destroyed, keep the IDoThingsService we created until we’re done with the API request in case something else needs it during this scope. Once we’re done with the API request, then destroy the IDoThingsService.”
Writing about technical things is hard to do well. These are some of my tips for communicating about technical things which should help whether we’re asking questions or giving answers or just providing documentation. Be VERY specific When writing about an issue, whether we’re asking a question or giving an answer, be very specific about… Continue reading Tips for Online Communication: How to Ask Good Questions and Give Good Answers
We end up needing to troubleshoot things because those things are doing something different than what was intended. This is my strategy for troubleshooting all the things, especially code. My first tip is to take notes. Write in a notebook. Type in a text document. Add comments to code that you won’t keep. Create unit tests… Continue reading How to Read Code When Troubleshooting
I’m a big fan of computers which is why I’m glad to be a Computer Scientist. I like to say that, because of my Computer Science degree, I can explain almost everything that happens from the time I press a letter key on my keyboard to the time that letter shows up on a website… Continue reading Why This Programmer Is Learning About Electricity
25 years ago Philippe Krutchen published an article in the IEEE Software magazine describing a different way to interpret and communicate software architecture. He used complex systems like air traffic control systems and phone systems in his example because those were the big, complex systems that needed this understanding at that time. For some context,… Continue reading 4+1 View Models of Software Architecture 25 Years Later
I was gonna sit down and write about how hard it is for me to spend at last 30 minutes once a week to sit down and write because there’s work to be done and OMG why aren’t I doing that work right now?! I was also going to publish my writing from last week… Continue reading Technology Makes This Easier All The Time
December 4th marked my one year anniversary as a software engineer/developer/programmer/coder and after a year I have learned a few things. One of those things is that job titles mean very little, especially in a startup but I’m getting ahead of myself. So here are some of the non-technical lessons I have learned about being… Continue reading Lessons I Learned My First Year As A Software Developer That Have Very Little To Do With Coding
