Software Development

A 12 post collection

Don't be a "Did it work? Yay! Ship it!" coder

 •  Filed under Programmer, Programming, Software, Software Development

I'm working on a longer post on what it means to write high quality code, but until that's done, I wanted to call out what I see as the tell-tale sign of less experienced programmers. It's when you see that "Did it work? Yay! Ship it!" quality to code. Let's call the person who does this, the DIWYSI coder.

So what are the signs of the DIWYSI coder?

The most obvious sign is lint, lazy writing or code structure, and lots of notes to self that never get acted upon. I don't mean that code has to be perfectly structured. I'm really not a perfectionist. It's just that someone who is only trying to get the code working and not thinking of other programmers is going to just hack, hack, hack, and once it works, commit and move on.

This kind of code often looks like:

    const thing = function someFun(){
      If ( something)
          // How does this even work?!?!
             Do_the_thing() }

This is exaggerated, of course, but it's not far off some stuff I've seen.

Keep this in mind -- great code is much more than just writing something that runs correctly. "Did it work?" should be the first question you ask, not the only question. If it doesn't run, then yeah, it's not good. Anyone working as a programmer today ought to be able to write code that runs. Writing code that runs and that another programmer can pick up and understand is much better.

Enterprise DevOps: What to Expect When You're DevOps'ing -- AWS Enterprise Collection

 •  Filed under Software Development, Engineering, Devops

Enterprise DevOps: What to Expect When You’re DevOps’ing — AWS Enterprise Collection

Some really, great quotable ideas here. Like:

start small and deliberately


Measure the impact of each organizational change you make

Finally, I really like the emphasis on this:

A DevOps culture should be conducive to smaller changes being made more frequently.

Best advice I can give coders

 •  Filed under Coding, Programming, Advice, Software Development

Don’t forget you’re writing code for other people to read. This is the single most important thing you can learn as a programmer. “Does it run?” is the minimum requirement for a good program. After it runs, spend the time needed to clean it up so it’s presentable and well-factored.

Even if you are coding by yourself, future you will thank you.

Coding, like any other form of writing, has an audience. Consider that audience when you write. Everything else about being a great programmer flows from this one simple idea.

Engineering Managers Should Code 30% of Their Time

 •  Filed under Software Development, Engineering, Management

Engineering Managers Should Code 30% of Their Time

Great tips here, and I generally agree with everything here. However, I’d suggest engineering managers should code more than 30%. I’d say they ought to manage 25-30% and code the rest. The thing that stops this happening is asking engineering managers to be product managers or project managers, or something more akin to a pure manager than an engineer.

Quite frankly, most tech companies have way too many engineering managers. Software companies need great engineers. Full stop. And, oh yeah, one or two should help keep the trains running on time. It’s really not that complicated.

Via @mjasay.