Skip to main content

2010: A New Hope

I couldn't have chosen a cheesier headline. I'm breaking my "How To ..." pattern of titles, but I figure this is probably for the best, and when better to make a refreshing change? I still want to post more How To articles, but I don't need to stick with the pattern for everything. It gets difficult to twist some titles into the right shape, anyway.

Prediction posts are always a big thing the week before and after January 1 and years ending with 0 always have even more of them. Why should I miss out on a great meme that only comes around once a decade? I'm going to mix it up a bit and give you more than a top ten predictions on some random topic:

Developing Upwards presents,

My Top Five Lists of Top Ten Predictions for 2010

This originally was written "My Top Ten Lists ...," but damn if I don't wanna do that!

I apologize for anyone who just let out a huge groan. You can skip them, if you want. The plan is to post one Top Ten Predictions list a day. I'll update the list linking to them here. I had a few conversations about predictions over the last week, and I really wanted to write them all down in one place.
This post is about a bit more than just some predictions and hand waving. This is also about a commitment: I need to commit to this blog more. This isn't some stupid blogger mentality that blogging is inherently awesome and should be the main focus of everything I do and make me lots of money. The facts are simple.

When I blog more, I am happier. The posts give me a means to reflect on what I've been working on and iron out thoughts that would only bounce around in my skull, otherwise. Getting things down on (virtual) paper gets them out of the destructive cycle of constantly bothering me. I think we should all commit to solidifying our thoughts more often.

Allowing title flexibility is a part of that. I'm not going to force myself to blog, but I'm going to put more into this than I used to. I hope to do more than that. The name change a while back was one part of a project that never got off the ground. I'll be moving this blog somewhere I can control the software and do things I can't or don't like the facilities for in Blogger.

I'll talk more about that in a post with more solidified thoughts.

Comments

Popular posts from this blog

Interrupting Coders Isn’t So Bad

Here’s a hot take: disrupting coders isn’t all that bad.

Some disruptions are certainly bad but they usually aren’t. The coder community has overblown the impact. A disruption can be a good thing. How harmful disruption might be a symptom of other problems.

There are different kinds of disruptions. They are caused by other coders on your team, managers and other non-coders, or meetings throughout the day.

The easiest example to debunk is a question from a fellow developer. Imagine someone walks over to your desk or they ping you on Slack, because they have “one quick question.” Do you get annoyed at the interruption when you were in the middle of something important? You help out your teammate quickly and get back to work, trying to pick up where you left off. That’s a kind of interruption we complain about frequently, but I’m not convinced this is all that bad.

You are being disrupted but your team, of which you are only one member of the whole unit, is working smoothly. You unstuck …

CARDIAC: The Cardboard Computer

I am just so excited about this.


CARDIAC. The Cardboard Computer. How cool is that? This piece of history is amazing and better than that: it is extremely accessible. This fantastic design was built in 1969 by David Hagelbarger at Bell Labs to explain what computers were to those who would otherwise have no exposure to them. Miraculously, the CARDIAC (CARDboard Interactive Aid to Computation) was able to actually function as a slow and rudimentary computer. 
One of the most fascinating aspects of this gem is that at the time of its publication the scope it was able to demonstrate was actually useful in explaining what a computer was. Could you imagine trying to explain computers today with anything close to the CARDIAC?

It had 100 memory locations and only ten instructions. The memory held signed 3-digit numbers (-999 through 999) and instructions could be encoded such that the first digit was the instruction and the second two digits were the address of memory to operate on. The only re…

How To Care If BSD, MIT, or GPL Licenses Are Used

The two recent posts about some individuals' choice of GPL versus others' preference for BSD and MIT style licensing has caused a lot of debate and response. I've seen everything as an interesting combination of very important topics being taken far too seriously and far too personally. All involved need to take a few steps back.

For the uninitiated and as a clarifier for the initiated, we're dealing with (basically) three categories of licensing when someone releases software (and/or its code):
Closed Source. Easiest to explain, because you just get nothing.GPL. If you get the software, you get the source code, you get to change it, and anything you combine it with must be under the same terms.MIT and BSD. If you get the software, you might get the source code, you get to change it, and you have no obligations about anything else you combine it with.The situation gets stickier when we look at those combinations and the transitions between them.

Use GPL code with Closed S…