During my performance review the other day, I confessed to my boss, Chad Stoker, that I didn’t consider myself a particularly gifted coder, just a very persistent hacker who sometimes has flashes of insight.
Case in point, today I finally pulled all the right pieces together to make a particular feature of my code work. It was one of those situations where my specific case wasn’t anything I could find on the interwebs, so I had to figure out which pieces to borrow from various examples and solutions and apply a bit of that persistent hacking. Sounds familiar, right?
- Dynamically create columns for a DataGridView table based on a dataset returned from my business layer, plus some other columns to contain buttons for customized actions.
- One of those additional buttons needs to open a new window, but also needed information available on the server side
This morning, I managed to poke the internet in a new way and find an easily understood potential solution. I carefully commented out previous code, put the solution in place, stepped through and VOILA! It works.
My Process: try something simple. Add complexity. Find limit of initial approach. Dig around on the internet, find new approach. Start simple. Add complexity. Find limit of approach. Stabbity stabbity stabbity. Go back to internet to find new approaches, fall down rabbit hole, climb back out, feel dazed and in need of a drink or a nap or both. Take walk, talk to oneself a lot about why you’re really not good at this work. Get new idea. Start simple, add complexity, etc. Eventually find way that works, is simple and easy to understand and that won’t embarrass you when you pass the code on to maintenance staff (hopefully).
There was a lot of stabbity yesterday. Today, so far, so good.
Tags: persistent hacking, stabbity stabbity