Career Advice
Author: Neil Green
Is It Worth Learning to Be a Software Developer in 2020?
Haters
My Perfect Business
CoffeeScript/Battojutsu
Brainstorming/Stoicism
WiT
WordPress/Code Pledge
Planting Seeds
Code Consistency
Atlanta
Non-Technical Development Managers Are Like Head-Chefs Who Can’t See, Taste, or Smell
I have made no secret of the fact that that I find non-technical managers useless in the delivery of software, but today while recording a podcast, I realize they have another fatal flaw: they can’t evaluate the performance of their team.
Read More »12 Types
Timelines
Generation Gaps
Capitalism
Leadership
Management
Rewrites
Breaks
Architecture
My Goal
Contact Tracing
Intentional Design
Gaslighting
DnI
10x
WFH
Remote and Junior
Coding Tests
Imposter Syndrome
Organizational Change
Agile’s Future
Arrogance
Quitting
Collaboration
Collective Ownership
Hackathons
Email Is Terrible
Email is the worst form of communication in common usage today. The only redeeming characteristic of email is to create proof that at some point in time, you tried to inform someone of something. In this way, it is very similar to its direct ancestor: paper mail delivered by the postal service, and it is just as obsolete. Unfortunately, as remote work has become an immediate necessity for millions of people worldwide, email has become a primary form of communication.
Read More »
Conference Call Sins: By Example
The following audio clips are examples of the most common mistakes people make during conference calls.
Read More »
What are Soft Skills?
Hard Skills are necessary to get a job, but Soft Skills are required to have a successful career.
Read More »
Agile History: Kent Beck vs. Alan Cooper
It can be argued that Scrum is the compromise Beck and Cooper had such trouble reaching in the following interview. As the original website where this was posted no longer exists, I copied the contents from the Internet Archives and reformatted it to improve the reading experience.
Read More »
Defending “Never raise a problem without a solution”
I want to offer a soft rebuttal to the article The Problem with Saying “Don’t Bring Me Problems, Bring Me Solutions. By “soft” I mean to say that I do not disagree with the thesis, only some of the implied assertions. Bear in mind that critiquing “Implied assertions” can be deeply unfair in a work that is intended to be taken literally.
Read More »
The Danger of ‘The Dark Sage’
JP Ventura left an intriguing comment on The Sage that I’d like to explore:
Read More »Considering each coin has two sides, what would be the dark side (i.e., opposite) of the Sage?
How to not get promoted
So you’re a high performer who likes their current position, but your boss keeps threatening to promote you so you can take on more responsibility. Here are some surefire ways to get them off your back.
Read More »
126 Soft Skills Every Developer Needs
The following are 126 soft skill topics divided into 14 categories. These are the topics covered in my SoftSkills.app training program.
Read More »
The relationship between determining technical feasibility and productivity
This is an answer to a question asked by Ashvini Chaudhari in the “Agile and Lean Software Development” LinkedIn group:
Read More »Dear All , I m pursuing my PhD in Agile Software Engineering. I have a question regarding spike solution ” If we add spike in project development will it have effect on team velocity? and if yes what could be the parameters ? All the responses will be consider as a general opinion in my PhD thesis.
I pity Tim Cook
It’s clear the Job’s deathbed playbook has long since been used up. The Apple devices are getting worse and worse year over year, but Tim Cook has managed to drive shareholder value despite that. Apple is the most valuable company in the world – no one can take that away from Tim Cook; but Apple has fallen from grace, and as captain of the ship Tim Cook bears all the blame.
Read More »
CoffeeScript is my Bullwhip
Define your problem before picking a solution
Our industry revels in coming up with solutions, but is quite poor at defining problems. This has resulted in an vast constellation of technological solutions, but with the majority of investment capital being centered around a small handful of banal consumer problems (Hailing Rides, Shopping Convenience, Entertainment, etc.) If we are to solve problems that are worth solving, we’re going to need to get better at defining our problems before we pick solutions.
Read More »
“Artificial Intelligence” is deeply disappointing, and so are we
The term “Artificial Intelligence” transitioned from Science Fiction to Product Marketing with very little time in-between to consider what exactly qualifies as “AI”. While tackling this definition has been done ad nauseam for hundreds of years, I believe that the modern definition of “AI” and those from Science Fiction are worlds apart. This is my attempt to bridge that gap.
Read More »
Why management will not change their open office layouts
The first study of how open offices affect communication has been conducted, and the results should not be that surprising. Open offices negatively impact productivity, and we’ve known that for a very long time.
Read More »
My response to “As a team lead how to handle project going off the rails?”
This is my response to a question posted on HackerNews.
Read More »
Let Loose your Lions
Enterprises complain about their inability to innovate at a pace that even approaches that of startups, and yet puts into place every system imaginable to prevent a team of Lions from forming and executing.
Read More »
How important is code quality vs. getting things done?
Anyone who lacks the knowledge of how to build quality software, as well as the wisdom to know when code is good enough to ship, does not have the experiential background to have a valuable opinion on the code quality vs. getting things done debate.
Read More »
Are we working or playing?
Recently I’ve been talking to companies that want me to improve staff productivity. The opening conversation tends to be about the same: they pitch me on their company and what a “great place to work” it is. They brag about how smart the people are, how much fun everyone has, and how it’s more like a family that a bunch of co-workers. They describe all the perks like massages, video games, beer-on-tap, coffee bars, and how much everyone loves them. “Sounds like you have it all together,” I say after hearing all of this. “Well,” they reply, “I just wish we could get a bit more out of them.”
Read More »
My Response to “How to *never* complete anything”
The following is my response to Ewan Valentine’s blog post “How to never complete anything” that I discovered on Hacker News. Once again, I ask for people’s indulgence for posting a reply on my own blog rather than in the Hacker News comments. I find writing on my own blog a bit easier than wading into the surf that is the sea of many perspectives.
Read More »
My Response to “Are we over complicating software development?”
This question was posted on HackerNews by ian0:
Read More »
A Far Too Brief Rough Outline of How to Approach Single-Date Estimation
In my previous “An Attempt at a Pragmatic Framework for Defining a ‘Senior Engineer’”, in the “A Process to Estimate Work” section I said:
“It is beyond the scope of this post to describe everything that goes into making a good estimate, but suffice to say a senior engineer views estimates as a difficult challenge to be surmounted, and as a result will normally ask for dedicated time simply to come up with the estimates.”
A commenter asked that I write an article on estimation, and this is my feeble attempt to do so.
Read More »
An Attempt at a Pragmatic Framework for Defining a “Senior Engineer”
Brandon Hays’ article “The Conjoined Triangles of Senior-Level Development” made me reflect on all of the Senior Engineers I’ve worked with. If I were to guess, these would be the shared traits that lead others to declaring them “Senior Engineers”:
Read More »