October 14, 2019
People. A room of people all engaged, all sharing the workload, all working towards a common goal. A team of people that don’t care what their roles are, only what has to get done. A group of people that are less concerned with individual skillsets but more concerned by what they can do if they all pitch in. We all know it, but we often forget just how we really get there (and how we do it consistently.
October 4, 2019
If you’re looking to be a Great Developer, here’s what you need to get started. Need Project Management Skills Need Requirement Skills Need People Management Skills Need QA Skills Need to know what to automate and when to start automating Need to have an eye on the future Need to be able to sell your solution to your team and customers Need to be prepared Need to stay up late Need to wake up early in the morning Need to manage your time Need to budget your expenses Need to plan for vacation (we don’t need any more burnouts) Need
September 30, 2019
No matter how great a developer you are, there is always going to be that one job that has to be done manually for it to work. You’re going to have to watch it. You’re going to have to babysit it. You’re going to have to be meticulous in what you do with it. You’re going to have to have patience and take your time. This is the tedious work, the grunt work, the work that you might feel is holding you back but that you know has to get done. Don’t ignore it, don’t wait for it to come
September 25, 2019
It’s taken for granted that you should be on time. I mean, someone went to the work of asking you to come to a meeting. They booked the room. They put together the agenda. They put everything in place to ensure that the time the team shares is spent usefully and not a complete waste of what everyone is trying to do. So why not be on time for that? If you decide that’s not enough for you and you still want to show up late and not on time, here’s the message you’re sending – “I don’t care enough
September 23, 2019
I received an email recently from a recruiter recently that only consisted of the title of the job in the subject line and a copied description in the body. No – hello. No – what’s up. No – what do you think. The goal was for me to respond with either a yes or no before a real conversation took place. That was the gate and it was up to me to decide what to do next, to see if this job title piqued my interest. The truth was it did, but ten minutes later I got an email from
