May 28, 2021
So am I. There are days I miss being stuck in traffic and listening to radio banter or my favourite podcast or simply going into auto-pilot as I make my way into the office. I’ve always enjoyed being remote with a sprinkling of on-site days to revitalize and refresh the memory – “Oh, that’s why we’re doing this.” This is a great convo on Remotely Prepared we’re having on that old commute. https://www.upsidedownoffice.com/podcast/the-remote-commute
May 25, 2021
In agile, there is a concept called “Capacity”, drilled down further to be in a per sprint cycle – “Sprint Capacity”. A sprint is a block of time in which you set out to accomplish a particular task, generally 2 – 3 weeks, capacity is the allocation you have to complete a certain amount of work in that time period. A typical developer, dedicated to one sprint (let’s say it is 2 weeks) might be 5 – 6 hours a day (giving leeway for some non-sprint meetings, bathroom breaks, and other things). From here you are looking at approximately 50
May 22, 2021
Having a pile of work, coupled with a fully booked calendar is enough to make you start hyperventilating. After all, you have deliverables that need to be done, and discussions that need to be had. The two are not mutually exclusive, both need to get done. The tendency is push one of the two off. “I need to work, these meetings can wait a week” And then those meetings turn into more work, fires, and emergencies because we pushed them off. We can delegate the work to others which would help get it done. Maybe we’ll have to review their
May 17, 2021
Not the company merge, but the CODE merge. Minor CODE merges aren’t a problem, but the big ones, the ones we have drifted so far apart on for too long, that we have been afraid to merge back in because “it’s not going to be run anytime soon” – those merges, those are the ones that strike fear into a developer’s heart. The first question a developer will ask is – “how long”? And if the answer isn’t “not long”, minds start racing with impacts and outcomes as to what might happen and ways to mitigate what will invariably happen.
May 16, 2021
I live in software where buzzwords abound and I can barely stand them. But – “Bleeding Edge” – this one gets me all the time. What we want to write code that is bleeding off the edge of a knife? Did someone die for our software to compile? Are we attacking Orcs at dawn? When I ship this code do I make a blood sacrifice to the elders of my keyboard? Oh wait, is this a Klingon thing? It must be, because all I can think of when I hear Bleeding Edge are these Ten Coding Commandments.
20 hours ago
Greg Thomas
Greg Thomas
3 days ago
Greg Thomas
