This is one of my absolute favorite topics to discuss in software development: Definition of Done in Software Development. While my approach is not fully flushed out for every environment, it’s gets you 90% there. This will help with creating a team and setting expectations. When is each team member actually done during the software development lifecycle? Have you found yourself saying, “well I know I said it was done, but it’s not really done?” Before we can start looking at each individual’s Done definition, we have to outline the members involved. Business Analyst Project Manager Development Manager UI/UX Engineer
Category: Software Developers
Going through Instagram, you’ll see thousands upon thousands of reels just related to #softwaredevelopment. Go to TikTok and it’s even worse. It could be that every single developer posts a reel every single day, but I doubt that’s true. Looking through tech company employee stats, you’ll realize that there are an insane amount of developers working at each firm. If there are that many developers, then why did everyone used to say that software development is hard? I started working as a developer in 2009, completely self-thought. Not having the developer support around me, or at least not knowing which
I frequently hear that there aren’t enough hours in the day to accomplish everything that I do on a daily basis. I love those. It’s all about organization. It’s so much about organization that I spend roughly 30 minutes each day thinking about how to improve my already organized life. It doesn’t take much, but with small increments, it adds up. Start with Jira You may think that Jira, or any other project management tool, should be used only at work. I’m here to tell you that you can project manage anything that you’d like, including your life. If this
Economic downturns have so far been my most profitable times. While everyone else is panicking, I get to work. Sometimes they’re career moves and other times they’re purely financial; most of the time they’re both. We’re in another pivotal time. How will you take advantage of the situation? What Most People Do There’s a saying that you’ve probably heard, “if it bleeds it leads.” This is the time that news organizations get excited about. They love the turmoil since people will be glued to their news station of choice. The market will continue to swing wildly and we’ll most likely
Why so many edge cases? Edge cases. You have to love them. It’s what will destroy your company and your employee’s morale. Chasing edge-cases can be a developers biggest pitfall if done in the wrong environment or their greatest strength if done in the right environment. How do you draw the balance and when? That’s what we’ll tackle in this article. If you haven’t read my article on MVP software development, I encourage you to do so. It covers thinking in MVP terms, which we’ll cover throughout this article. What is an Edge Case? The best way that I can
Stop Living Life Like There’s a Deadline. It’s no lie that by the time you’re 35, you want nothing to do with writing code professionally. When I was in my early 20s, I thought that I would write code forever. Nothing seems more appealing than spending 8–12 hours each day writing code or learning about development. Those were exciting times; I’m sure you’re going through the same thing, or you’ve been through it already. If you do it for long enough, you will burn out and that’s when it starts going down hill. Signs That You’re Overdoing It Sleeping Less.
Are you ready to end your career? Test scenario: for the next 3 months bring only problems to your boss. Talk about all of the imperfections in the company. State that the organization would be drastically better under different leadership. You won’t last 3 months. Only try the above if you really are striving for unemployment. Get ready for the ultimate Developer Career Killer. Your Concerns Could Be Legitimate We won’t dwell on individuals who really do just complain for the sake of complaining; we can’t rescue them. You’ve actually seen something wrong within the organization and you want to
Hindsight is 20/20 When you’re a first time developer, everything is exciting and scary at the same time. You look at your Senior Software Engineering counterparts and wonder if you’ll ever make it to that level. It takes a few years to understand the ins-and-outs of the business, but once you’re there you realize how hard on yourself you actually were. These are the 10 Programming Tips I wish someone told me. 1. You Can’t Learn Everything You don’t know what you don’t know. It seems like you can just keep studying and you’ll know everything there is to know
The reasons are simple I worked with hundreds of developers over the last 15 years. The one thing that they all had in common, myself included, is stress. I was about 5 years into my development career when I felt so stressed that I knew it would soon start affecting my health. I was able to reflect and cope with it, mainly through books such as “Don’t Stress the Small Stuff and It’s All Small Stuff” and “The Mindfulness Solution.” Those 2 books changed my life. There are many legitimate reasons for developer burnout: Deadlines Legacy Applications New Programming Language/Framework