Software Development’s Post

This happens all too often and if often causes burnout and frustration in the tech world! Unfortunately, this is the reality for a lot of new people. Their new companies codebase is gigantic and messy and tough to work with and of course there's no documentation! This isn't how it should be, but that is the reality for a lot of people. My advice is this: 1. Ask a lot of questions to your manager and coworkers on how their code works and why it was written that way. 2. Point out redundancies, inconsistencies, inefficiencies to your boss... and then offer suggestions on how to fix them (or if you don't know, ask how you can work with them to fix them) 3. Take things slow. You can't understand it all in one day. Things are more complex than it looks like on the outside. So give yourself some grace and know it'll take time. 2 weeks is not enough to understand! Give yourself about 2-3 months. Starting a new role is challenging enough, especially when the company is not perfect or have all their ducks in a row. Although the secret is that this is 100% of companies. No company will be perfect.

#4 When starting a new data role, if there is no documentation or you are not provided documentation, make documentation as you go. This will help you in a few ways: 1. It will give you some mental space to reduce trying to track all the details about what you are learning about source, target, ETL, ownership, etc. 2. You can build up something you can show yourself and your manager that you are moving forward from your first day. 3. If you find a SME or someone who worked on the data processes before you, then you can specifically talk about certain areas if needed, enabling productive and focused conversations. Alex is 100% right about all data work everywhere having some degree of unknown. By documenting what you find as you find it, you also pay it forward for the next person. #dataanalyst #dataengineering #successmindset

If been to the same place, just with a 4000 line cypher script. About the mental part I’d suggest to reframe the work: It’s actually an incredibly complex task, which not everybody is capable of performing. It’s much harder to produce good results here, as it would be just to produce new code. So, try to frame it as a challenge and a very good training for your skills. After all on successful completion, you’ll be an expert. I know that such a task is very frustrating. Usually in projects like this, there is a reason why something has emerged in such a way - and more importantly - why it has not been corrected in a long time. Usually making changes to such a beast is not possible at all. Too much undocumented information is captured there. Probably the only way to tackle this is to go into very structured analysis of the code and produce a well-defined functional requirement analysis. Based on them, you can implement a clean implementation (optimally with test cases). However, that would require a code-freeze on this query so that no one applies changes to it while reworking it. One way of action may be to talk to the management to sensitize them about the large risk for the project.

How to burnout a software engineer, in 3 easy steps https://buff.ly/48QvnF3 #softwaredevelopment #developer

How can software developers avoid burnout? 👇 Here are my views based on my experience - 🔹Enjoy the work you do. 🔹Take breaks, there's no need to push yourself unnecessarily. 🔹Discuss things with your peers, it really helps. Good luck! And don't forget to take care of your health. What are your thoughts??? #softwaredevelopment #mentalhealth #stressmanagement #softwareengineering

Burn-out in software engineering is often an insidious process. It creeps up, until at some point it becomes all consuming. If you're a software developer, or if you manage a team of software developers, here's how you make sure that burn-out occurs: https://lnkd.in/gu-Wp6hA

🙃 In Tech, it can be extraordinarily difficult to keep up with shifting priorities, on-call schedule, bug fixing, the current sprint, etc. Add in life goals, personal responsibilities, or extracurriculars and it's enough to make anyone's head spin! Unfortunately, we know these things aren't going away any time soon. So, what can we do? We can improve our systems for dealing with this 'day-to-day'. If I had to recommend one change you could make to improve your personal productivity, it would be to start using a simple to-do list. 📓 For the last 6 months, I have carried around a notebook. Each morning before I begin my day (after grabbing a fresh cup of coffee), I turn to a new page in my notebook and write the date. Then, I write "work" on the left page, and "personal" on the right page. I'll sit for 10-15 minutes and write out any of my priorities for the day, loosely organizing them into an ordered list. Throughout my day, any new priorities are added to list. Some days there are more or less items. Some as complicated as "Upgrade DB to MySQL 8" and some as simple as "Take a walk on lunch break" but they're all represented. As I complete the tasks, they're crossed off the list. If they don't get done, they get circled, indicating they're push to the following day. This notebook is very much my own little daily Kanban board. 🎆 It's simple but it works! My productivity has sky-rocketed, I remember to stretch throughout the day, to eat meals at set times. I'm not forgetting smaller tasks at work because I can just write them down quickly in my notebook that's always at hand. I'm happier overall because I can see at a glance what I've achieved in a day, I'm sure I'm not dropping the ball on anything, and I can ensure I'm making progress towards what matters to me most. So, in 2024, try a to-do list! #softwareengineering #tech #devops #sre

There are few tips to help you overcome burnout as a software engineer. 1.Know When to Take a Break. ... 2.Become Replaceable. ... 3.Be More Efficient. ... 4.Learn to Say No. ... 5.Set Reasonable Goals. ... 6.Prioritize Your Health. ... 7.Don't Neglect Your Life Outside of Work. ... 8.Learn Something New. #softwareengineer #software #corporate #company #IT #developer

In software engineering, burnout is a significant hurdle in maintaining high-performance teams. The article 'How to Burnout a Software Engineer' (link below) sheds light on this pervasive issue!

Measuring the wrong things can destroy developer motivation and productivity. That’s why developer stack ranking based on nonsense numbers — like the number of commits or pull requests — often does more harm than good. In this blog post, we discuss a healthier way to gain visibility into the work of software engineers.