Princeton University led by Andrew Appel just received a 10 million dollar grant from the National Science Foundation to explore tools and processes to completely eliminate the software bug. The basic idea is that all bugs originate from differences between the software specification, and how the code is written. The researchers hope to do all this through a tool called DeepSpec.
The premise of this research is a scam, anyone with a few years of experience in software could tell you that. That is a pretty hard statement, let me explain.
– Every career advice answer to a forum question on the internet, ever
Okay, maybe not ever, but this is the standard advice to any problem at work. On the surface, it certainly seems reasonable. Perhaps a bit obvious, the core of this message is: You’re gonna have to do something.
Here at Uncharted Waters, we take a second look at conventional wisdom, putting it to the dark room test. That is, if instead of listening to that one-hour presentation (or reading that ten-page forum post) if we just sat in a dark room to think, could we come up with answers as good or better? Sometimes the answer is ‘no.’
Sometimes it’s yes.
Today I’d like to take a look at one piece of the conventional advice answer: FU Money, how the pursuit of it could actually be holding you back, and something better. Continued »
I love holiday travel. The airports are overcrowded, planes are running late, and families are trying to round everyone up to the right place at the right time so they can get back home. It is basically the perfect environment for noticing something out of the ordinary. I’m a (mostly) loyal SouthWest customer. They have good customer service, and reasonable rates. On my flight last week, I also happened to notice that they take kaizen seriously.
Kaizen is a word we took from the Japanese invention of Lean process after World War 2. There are different interpretations, and methods that may or may not be mandatory depending on who you talk to, but the most important part is experimentation and discovering what can be done better.
Lets take a look at an example of how SouthWest changes things and aims for efficiency.
It’s performance review season.
The temperature outside has been steadily dropping for a month now. Unless you’re in California or Florida, you probably have to let the car run for a minute to melt off ice on the windshield. Instead of having a few more hours of sunlight each day at the end of work, it’s pitch black and may as well be midnight.
You know that that means, and it isn’t a signal for Santa’s arrival.
Everyone hates them. For managers it is a month long time suck of paperwork, dividing up a shrinking budget, and reviewing work that may have happened 9 or 10 months ago. For employees, it’s a time to strategically talk about the work you did. You want to give an honest review, but not so much that you kill your chances of getting more money for the next year.
How do you turn the yearly performance review into something that works for, instead of against you.
There has been a lot of research lately on the effects of sitting all day on a persons health and fitness. We really don’t need research to see this. Most people that spend most of their time in front of a computer slowly feel what is happening to their waist line and more importantly, their long term health. We get out of breath going up a couple flights of stairs, picking up the kids gets a little harder and more tiring, household chores leave us sore.
I don’t have any suggestions for Christmas gifts this year, Matt can help you in that department. But, I do have some fitness suggestions to keep you healthy and happy for years to come.
“Startups” are the new cool place to be.
But what are they?
For today, let’s define a startup as a company with potential for massive profits but an unproven business model. (Our senior contributor, Matt Heusser, likes to point out the definition of a proven business model, that you can drop a dollar in advertising in and a dollar fifty comes back. If the investment of the next five million dollars has risk involved … you’re probably a startup.)
Today I’d like to take a look at the forces around startups, using the example of mobile application sold in the play store, through the lens of Michael Porter’s Five Forces competitive model.
Imagine working at a small software start up. There are maybe 10 people at this point and everyone feels like they are a part of something; owners of a living, breathing thing. Your little company is doing well. The team is building good software and the market is responding with “yes, more!” by throwing money your way.
Now, it’s time to grow the company and scale up your efforts. You need more developers, more sales people, and more software to sell.
How do you keep the magic? How do you take a small set if ideas that work well, and grow them to work in a company that has not 10s, but hundreds or thousands of employees?
This is the question that the book Scaling Excellence: Getting To More Without Settling For Less tries to address.
Let’s take a deeper look and see if the scaling problem can be solved so easily.
It’s December, a time when programmers, sysadmins, testers, and managers (especially managers) think about getting a thing or two for a person or two.
You might give up and get nothing; I certainly did enough of that my first decade in IT.
You could spend a hour asking Amazon for ideas, all of which seem not quite right, or give up in five minutes with a USB stick or Tux Stress Toy.
Or you could hang on for a few ideas that might be a little too silly, a little too business, or, perhaps, just right.
Agile came about as a response to the extreme standardization of software development process that was popular through the early 2000s. That standardization mostly came in the form of waterfall and Rational Unified Process (RUP).
The principles of agile suggested the exact opposite of processes like RUP and waterfall. Instead of a one size fits all approach, we now have extreme customization. There is no common starting place and every team applies the principles just a little different — some use scrum, some use kanban, some TDD here, and a CI system there.
Managers noticed that loosening up on standardization got software done faster and want to spread that goodness through their company.
There is a problem though, agile doesn’t scale.
Back in 1993, I performed my last show as a professional musician. This had been an endeavor that I had pursued, quite doggedly, for the better part of a decade. I had a number of successes and failures along the way, and I learned a lot of skills that would serve me well in my future career as a software tester.
The past few weeks have brought me full circle, in that I accepted an opportunity to perform with a band once again. One of my former band mates reached out to me and told me about a project that he was working on, and asked if I’d be interested in coming “out of retirement” to sing once again. After considering the time commitment and the logistics, as well as the technical challenges involved, I said “Sure, let’s do this!”
I have always believed that my time as a musician, as well as performing in a band, was critical to my success as a software tester and my ability to work in IT in general. That may sound like a strange way to come to an IT career, but in truth, the two disciplines (music and Information Technology) are surprisingly compatible. Both are creative spaces. IF you have never considered IT a creative space, think about the way that problems are often solved, and the way that solutions are derived. Very often, the logical and first planned approach doesn’t work the way that you anticipated it would. Musicians are taught to improvise early on, and often a performance can go sour rapidly if they cannot think on their feet if a problem occurs.