It seems that in every tutorial, the first task is to print the words "Hello World!" in some fashion. Every tutorial for every language, framework, etc. has the same task. Why? Because it's the hook. The thing that gets you invested. You start thinking to yourself, "Look how easy that was! I can do anything with this shiny new tool!" This first post is no different. It's testing the waters for my new blog.
I've been a software engineer for more than a score (that's 20 years if you don't speak 19th century English) and I've seen fads come and go. I've been in arguments about "The one true way" only to find that my understanding had been lacking. I don't do that as much anymore, since I've broadened my horizons by learning new tools and ways of thinking about writing software. What I've learned over the years is that Albert Einstein got it right when he said, "Everything should be made as simple as possible, but no simpler." (paraphrased).
One thing that I've marveled at is the changing definition of what we consider "simple". With some software stacks (I'm looking at you, Java) you don't start reaping the benefits until you've spent the greater part of a week just to get the environment set up. Meanwhile over in other parts of the development universe, people can get set up in less than a day and start being productive right away.
I'll be slowly writing about software I will be releasing to the wold at large, and hopefully, my philosophies surrounding software development will be reflected well enough. I like simplicity, and I like the things I use to let me design my software any way I choose. Some libraries are great for this, and some are not (full stack frameworks anyone?). There's always a trade-off, so I like to make it clear what you give up for the convenience I provide.
I've been a software engineer for more than a score (that's 20 years if you don't speak 19th century English) and I've seen fads come and go. I've been in arguments about "The one true way" only to find that my understanding had been lacking. I don't do that as much anymore, since I've broadened my horizons by learning new tools and ways of thinking about writing software. What I've learned over the years is that Albert Einstein got it right when he said, "Everything should be made as simple as possible, but no simpler." (paraphrased).
One thing that I've marveled at is the changing definition of what we consider "simple". With some software stacks (I'm looking at you, Java) you don't start reaping the benefits until you've spent the greater part of a week just to get the environment set up. Meanwhile over in other parts of the development universe, people can get set up in less than a day and start being productive right away.
I'll be slowly writing about software I will be releasing to the wold at large, and hopefully, my philosophies surrounding software development will be reflected well enough. I like simplicity, and I like the things I use to let me design my software any way I choose. Some libraries are great for this, and some are not (full stack frameworks anyone?). There's always a trade-off, so I like to make it clear what you give up for the convenience I provide.
looking forward to more enlightenment!
ReplyDelete