I recently taught a class at a bootcamp where a large part of their program was developed around the concept of a "Growth Mindset".
We recently interviewed David Wood on our podcast Getting Apps Done, and during the conversation David reframed "technical debt" as "technical credit".
Compromise and Test
In my previous post, Choice of Priorities, I talked about what to do when presented with a question of priorities. I argue that the answer is to do "both". But what about when those two priorities are mutually exclusive? "Do we make the button green or orange?" You can't really do both in this case, right?
The Choice of Priorities
Recently my daily feed was filled with a discussion about "What's more important? Writing maintainable software, or shipping software?"
Your interview questions are awful (but we can fix them)
The first time I was involved in a technical interview I was asked to present and grade a coding question: "What does this script do?" The candidate was then handed a print out of a (relatively) simple VBScript that changed the computer name of a Windows PC.
Only one candidate answered correctly. Every other candidate failed the question with an "I don't know."
On first glance, this seems a reasonable question. Part of the job they were interviewing for often required working with scripts to deploy computers and software. I told them that we weren't looking for a specific answer, just a general idea of "What does this do?" The candidate failing to even make a guess seems like an interview fail. They couldn't think on their feet. They couldn't think creatively.
But was it really a failure of the interviewee?
The goal of this post is to present a relatively simple agile-like development process to get started with.
The main audience is new Project/Product managers or developers trying to wrangle a chaotic development cycle.
No one likes a new process. It's work to memorize, it's work to do, and it removes your own autonomy from a situation, keeping you from just doing whatever you want to do.
But working without a process leads to chaos. Missed deadlines. Solutions that don't actually solve the problem. Angry customers. Angry managers. Angry developers.
The 1.0 release of PingPongr was pushed to NuGet a while ago. Since its initial release the framework has been reworked to use .NET Standard 2.0 which has simplified and standardized the basic use cases.
React and Redux
For the longest time after React was released I had difficulty really understanding how it was supposed to be used. Coming from years of MVC/MVVM experience in Java, C#/WPF, and Angular, React seemed strange. The basic tutorials and examples showed 'how' you do something, but never why, and there was pretty much no separation between view and controller logic.
Eventually I sat down and wrote something using React and Redux, following the 'best practices', so I could understand the decisions that went into the frameworks and how they could be used.
Over the break, I wanted to build a quick nutrition web app. That's not what end up happening.
Monty Hall Puzzle
Wikipedia has an excellent article on the “probability puzzle” know as the Monty Hall problem.
It’s based around the concept of a game show where a contestant must pick one of three doors. Behind one of the doors is the prize. When the contestant picks the door, the host opens one of the other doors that doesn’t have the prize and then asks the contestant if they want to switch their choice. The question: Do you switch or not?
In my day job, I spend a lot of time coding core business logic applications. What do you do with data A in situation B kind of logic. So when I work on something code related in my off time, I like to putz with technologies outside of that bubble.
With that in mind, I'm going to talk about animation.
Typescript and Visual Studio
Hello and welcome to the requisite "New Blog" post. This is the first blog I've set up in awhile, and the technologies used may be interesting to some.