General Commentary – Page 9 – Software and Other Shenanigans

All hail managed services (or at least good VM automation)

General Commentary, Java, Programming, Work No Responses »

Aug 022016

I transferred teams at work recently, and spent about a week trying to get their code running on my laptop so I can do useful development work. This is in addition to trying to wrap my head around the existing codebase and figuring out how to test my changes. It’s not that the code is bad, it’s just getting all the ****ing components hooked up, communicating with each other, and playing nicely together an exercise in impossibility. Coming from a group that ran everything in AWS, going back to managing all the third-party services in a development environment makes me want to flip my desk over and start screaming about what the **** is wrong with everyone.

If your goal is to “disrupt” something, you’re doing it wrong

General Commentary No Responses »

Jun 282016

1 of the most common themes around any startup these days is how they intend to “disrupt” something. Founders aren’t saying they plan to “disrupt” something as a consequence of what they’re doing, but rather using the term like it’s an actual objective – “disrupt the {industry name here} industry.” Here’s the problem, I don’t go into a store, online, or pay people to disrupt something, I pay people to either give me a thing that I find useful or at the very least want, or to do something that makes my life better in some way. “Disruption” isn’t either of those things. Continue reading »

Good logging is an art that I wished I had learned in school

General Commentary, Programming, Work 1 Response »

May 272016

You’re sitting there at work and word reaches you that your application is misbehaving. What’s the first thing you do? Pull up the logs and see what they say. And this is where you may wish that you had an entire class in school dedicated to the art of writing useful log messages. Good logging is an art, and it’s 1 that most of us don’t learn until we’re stuck trying to diagnose something in the wild with subpar messages to guide us.

Inter-project dependency management – is that even a thing?

General Commentary, Projects 2 Responses »

Mar 232016

So I ran into an interesting issue a while back doing something on a project at work. I was doing something that involved interacting with files on S3, and had updated the AWS libraries my application was using, but I was running into errors every time I tried to do anything that touched S3. The issue wound up being a dependency conflict between my code and an S3 wrapper utility we wrote around the AWS SDK. While the main project’s AWS SDK was up-to-date, the utility had older versions that were causing the errors. Although I had used Amazon’s BOM and thought that made sure that my AWS libraries were all set to a particular version, the reality was that assurance didn’t spread to other libraries my project pulled in. The solution was simple enough – update the AWS SDK versions in our other internal library, but that did lead to the question, how does one manage dependencies between projects?

Don’t use DynamoDB as a production database

General Commentary, Work 4 Responses »

Feb 232016

Amazon’s DynamoDB service is a managed NoSQL database that promises great speeds that allow it to be “…a great fit for mobile, web, gaming, ad tech, IoT, and many other applications.” That claim is pretty much just a pipe dream. The reality is that DynamoDB is a terrible fit for most applications, and your best bet would be to prefer regular NoSQL databases and manage the machines yourself.

How do you solve a problem like sample data?

General Commentary, Work 1 Response »

Dec 172015

It’s a tale as old as development – you make an application, and now you need to sell it. That means you need to have a demo, and demos require data in there. The dilemma is, what do you do to get that data? Do you have a demo app in a sandboxed environment, do you just add it to your regular production database, do you just take some screenshots of what the app looks like with data from a development environment, or do you do something else entirely? It seems like a stupid thing to worry about, until you’re actually trying to figure it out, then it becomes really important because whatever you decide to do about sample data, you’re going to have to live with forever.

A special thank-you to the people who make good software possible

General Commentary No Responses »

Nov 262015

Since ’tis the season of Thanksgiving, I wanted to offer up a special thank-you to the unsung heroes of any software development project. They’re vital to a good final product, yet most of the time nobody ever realizes the impact they had on getting your software where it is today. So, in the interest of spreading the thanks and love all around, thank you to all the people who aren’t “dev” or “ops” that make all this possible.

The ups and downs of social voting

General Commentary, Shenanigans No Responses »

Oct 232015

My friend Warren Myers had an interesting blog post on voting mechanics on various websites, along with “like” mechanic various social networks use (like buttons, +1 buttons, tweet favorites, etc.). I’ve made my feelings on things such as “like” buttons known, so I’m not going to go into those here. Warren raises some good points about the issues with voting on a lot of sites, but there are some places where I think works well that I think are worth noting, along with why they seem to work well. It’s important to note these reasons if you want to make sure your voting mechanic improves your site.

You are not a stakeholder

General Commentary, Shenanigans 1 Response »

Jun 202015

If you’ve worked long enough, you’ve hit on something that involves multiple people. At that point, the common line is to “get all the stakeholders” together so everyone’s on the same page and actually working together. It’s a good philosophy, that works when you’re getting just the people involved in something together – and nobody else. The problem is that that’s rarely how these situations play out. Continue reading »

News flash, terrible programmers are hardly “secret”

General Commentary, Programming, Work 3 Responses »

Apr 142015

TechCrunch had 2 articles last month on “Secretly terrible engineers.” Reading the articles makes it sound like there’s a serious problem with how we interview software engineers. Personally, I just don’t see it. Software engineers are like every other profession, the people in it range from terrible to amazing, and the which engineer is which is hardly a secret. Likewise, having just gone through the interview process within the past year, I haven’t really encountered the issues Danny Crichton described. Granted, I wouldn’t interview anywhere near Silicon Valley, so my geography could be affecting what I observed, or I could just be absurdly lucky, but somehow I doubt it. Continue reading »

Older Entries Newer Entries