Skip to content

Tag: programmer

On Giving the Atlanta Code Camp Talk

Last October I was accepted to speak at the 2015 Atlanta Code Camp on keeping clean code.  It was a really great experience, I would definitely recommend this conference for anyone who wants to speak at tech events. I’ve been to this conference in the past, but this is the first time I’ve been a speaker. The organizers of the conference were on top of things, and they made sure I had everything I needed prior to my presentation. And knowing I was a bit nervous about giving my talk, they checked in with me afterwards. The speakers’ dinner, the…

DroidScript Fun @ GDG

This week’s Mercer/Macon Google Developer Group was hosted at SparkMacon, and my friend and coworker, Michael Rosario, was presenting on DroidScripts. This is Michael. DroidScripts lets you write android apps with JavaScript. Ya know, if you’re really into JavaScript. But it really does seems to be a good alternative to regular Java/Android, if you’re looking to do some quick prototyping. There’s no manifest file to futz around with and hardly any setup before coding. (Bee tee dubs, I called the “manifest” file the “manifesto” file for the longest time. And nobody corrected me, seriously? lol.) The IDE you develop in is browser based,…

Your code is bad… Take care of it

  Refactoring is often not done. “There is not enough time”.  “Its not your responsibility”.  Look. Refactoring can only *help* you. You don’t need to devote hours and hours to it. Just make small changes. And over time your code will improve. And for the most part. Most of us are not writing NEW code. We are maintaining code. (And you probably should not be trying to write MORE code, but that’s another story). And its likely you will be working in the same code base for the duration of your employment, or will eventually be called to return to it.…

3 (Nearly) Effortless Ways to Keep Code Clean

Keeping code clean does not have to be a huge endeavor. Just do a little bit at a time, and your code will be shiny in no time. Consistency in naming variable. From the database, to the middle layer, to the user interface. If they are the same thing, do not change up the naming. It will make it so much easier for both you and other people to follow the code. Delete commented out code. If the build is working without the commented code, then you don’t need it. Maybe it’s someone else’s code. But if it’s been there…