Yes, but this is before CGI.
deathmetal27
joined 1 year ago
Anyway: What makes the difference for me: taking the time to think about proper solutions. Let some problems rest for a day and reevaluate the things I made the day before, before review, merge or deployments.
I agree, I do this when I am designing some new module. I tend to write detailed design documents, covering as much behaviour as possible. I then get it reviewed by someone who might have a good understanding of the business process related to the change. This is not very feasible for legacy code because often there is no proper documentation or comments. What I'd prefer in such cases is to implement new modules in a manner where it lies somewhere outside the legacy body of code (different package or module) and expose functions to hook into the legacy code. This way at least the new enhancements follow best practices and don't become just another patchwork to the increasingly unmaintainable legacy code.
Back to your original problem: legacy code like that is probably hard for everyone but it makes a difference in what pace (or patience!) you are doing your work. I think medication can help you with that :)
True. I have been thinking of resuming medication myself.
I don't exactly draw flow charts, mostly because the nodes don't make sense to me without context. Instead, I read a few lines, understand what's going on there and then write down the gist of what I understood. I write these down as bullet points with nesting to track branching code. If still find it pretty cumbersome.
TBH, this wouldn't have been that big of an issue if the code was commented or documented properly. But then again, who is going to go into code written back in 2018 to document lol.
I also have some level of aphantasia so I can’t visualize a workflow that I didn’t create
I'm sure it's much more common among developers to not understand another developer's code.
I do mutter the behaviour of the code to myself when studying like you described.
I already gave feedback to my manager that we were having too many meetings on the same day, so now they are spread evenly over the week. Usually they are not more than 30 mins.
As for caffeine, I think I have developed a tolerance. I have two cups every day and it feels like it hardly helps. I should probably get back on the meds though.
I agree that maintainability is important but the issue is that the team lacks that level of (professional) maturity. Actually they used to avoid writing design documents until I joined the organization and made everyone start doing it. They would simply see the user story and then get to work on the code. We're talking about code written back in 2018 by some contractors, getting patched till today until it's now spaghetti with meatballs and ragu on top.
I am planning a training session on DDD and clean architecture for the team so hopefully they will improve later.
Yeah, I use bookmarks and mnemonic bookmarks as well.
Creating a rough git branch is a good idea though, I should do that. Currently, I try not to modify the code too much when studying so that the code because I would later have to revert them back otherwise it would confuse the PR reviewers if there are too many formatting changes not relevant to required changes.
I avoid adding logs because after I'm done, I will have to remove them otherwise my PRs will be very big depending on how many files I have to update. I instead track the call hierarchy of the function I am studying using a feature in the IDE. It basically creates a tree of all functions called by a function, which helps me track how deep I am and how I got to where I am currently.
I should probably resume my medication though.
Context: Around the 1920s, German architect Herman Sörgel came up with an idea to drain water from the Mediterranean sea by building a dam across the strait of Gibraltar, among other places. The goal was to reduce the sea level enough to claim more land from the sea and bring Europe closer to Africa so that Europe could colonize it and hedge against the growing power of the US post WW1. However, with the fall of colonialism and invention of nuclear power after WW2, the idea lost support.
Context: Towards the tail end of WW2, the Luftwaffe created a task force called the Sonderkommando Elbe to slow down the Allies' bombing. They did so by replacing the rotors on their planes with those made of steel and ramming bombers in critical locations. However, unlike the Kamikaze pilots who were expected to die, the Sonderkommando Elbe pilots were trained to bail before or after ramming their targets so that they could fly again.
Context: Whenever a new Ottoman sultan comes to power, it was customary to have all of his brothers imprisoned or executed so that they cannot depose him or be used to depose him by others. In fact, his brothers would be imprisoned as soon as he was declared heir in anticipation of becoming sultan.
Context: Towards the end of the Horus Heresy, most of the traitor forces were engaged in sieging the imperial palace. The Emperor's Children however were instead terrorizing the citizens for their own pleasure.
Generated this using animorphgenerator.com
So blame the weird layout on them.
In 2023, I had 97% Linux with the only Windows games being Skyrim and Fallout 4 because of modding.
Now that I got modding to work on Linux I resolved to have 100% playtime on Linux for 2024. But Steam Replay says nothing because its still only one device :(.
Gaben, throw us a bone here pls.
view more: next ›
We need more Grickle here.