Whenever I’m talking with someone about future prospects, be it a fellow student, colleague or potential employer it always ends up at what I want. And well, until now I haven’t really been able to figure it out. Somehow I had hoped that talking to a lot of people and checking out a lot of interesting companies would help me realize where in the future I want to be.
But when I finally figured it out I realized that I don’t really care so much about what I’m doing, it’s more about how. I don’t care so much if it’s consulting or in-house, if it’s business and logistics or game development. What I really want is to end up where I have colleagues that can always teach me something new. No matter how long I stay at one place I still want to be able to pick up and learn new stuff as if it was my first month there.
For me the fun part isn’t so much about the result as it is about finding the best way to solve the problem at hand. And the more I learn the better I become at finding different ways to solve problems, which is what I really want to do.
I have been using a lot of different frameworks for several years now and I am stumped by how many of my fellow programmers have done the same but still don’t know about micro-frameworks.
A lot of programmers learns how to use one large framework that works for 99% of projects and use it as a boilerplate for everything they work on. In a team of developers, this is actually a good thing. It creates consistency between all projects and allows for easier reuse of code, it also means that everyone on the team are forced to use the same tools and environment to work in. This makes collaboration easier as everybody’s code will look more alike.
However, when working on a smaller project of very limited scope it might actually be quite cumbersome to set up all the configuration and code required to get a large framework running, especially if you don’t already know a framework for the platform you’re developing on. In this case a micro-framework might actually be a better idea.
I have a good example of the usefulness of micro-frameworks on GitHub here. This is a project I made to store and list links reported by an IRC bot so they can be browsed later. The entire application logic is in a single file of 117 lines of code that includes database configuration, routing, template engine, REST API, authentication and more.
Since micro-frameworks aim for minimalism they’re faster and easier to get started with and allows the programmer to get started with the project earlier. The pay-off is that the project structure can get quite messy and possibly unstable if the scope of the project grows too much.
I was very hesitant to create an about page at first when I started working on my blog or webspace or whatever you call it. It really seemed like a huge waste of time to put down even a small bit of effort to create something no one would ever read, I know that I myself have very rarely read people’s (or even companies) about pages. But still it might be good to actually have one if someone would stumble in and wanted to know more about me, who knows what opportunities I might miss otherwise.
So yeah, I was very conflicted about creating an about page for actually really silly reasons but what I finally did was that I created an empty page and labeled it “About me”. I then waited to see if anyone even looked at it. It turns out that a visitor is more likely to go to the about page after reading a post than going to the front page, YMMV. It didn’t take long for me to sit down and put in some content after that.
This was actually a few years ago and I do have a pretty decent about page now.
My site has been missing sharing buttons for over a full year now. After reading an article about how people so rarely use sharing buttons on pages that they only serve to clutter up the site and distract from the content I decided to remove them.
The point of the article was that the visitor would be more likely to copy and paste the URL than use the embedded buttons on the site to share the content. I can’t even find the article now, but this tweet from Smashing Magazine was also very influential in my decision (only now do I realize that they were talking about the stupid like button and not the sharing tools).
We removed FB buttons and traffic from Facebook increased. Reason: instead of “liking” articles, readers share it on their timeleine.
But I recently found an article on Reddit which I thought was very interesting and wanted to share. Realizing how annoying it would be to copy the link, navigate to another site and paste it there I actually wanted to use those sharing buttons. Which, funny enough, where so difficult to find it was actually more trouble than my original plan.
This finally led to me to re-enable the things. One of the many upsides of using WordPress is that you can use their phenomenal Jetpack plugin which actually has some really elegant buttons, which actually don’t clutter up the page so much.
Admittedly, it’s not a complete solution if you need it on a page with more than one textarea though. Then it goes from a one-liner to a three-liner.
I’ve had an issue with my phone where double clicking the headphone control button won’t only skip to the next track but will also redial my last phone call. Apparently this is because of some of HTC’s customizations which doesn’t really make sense to me.
However it’s very easily fixed by installing a third-party app like JAYS Headset Control or Headset Button Controller. But, needless to say, default configurations like these are extremely annoying and it’s difficult to understand why some phone makers seem to feel so obligated to change working defaults without even including settings to restore the original behavior.