I feel like these memes have to (mainly) stem from badly documented or broken libraries. The only times where I don’t understand what I’m doing are when I try to figure out what someone else is doing
The most recent library I wrote for my team at work is painstakingly documented, and everyone has been invited to the multiple recorded training sessions.
They still act like it’s black magic and just push all work and questions to me.
Lol, welcome to the party. I’m not in a programming position, I’m on a systems engineering team. Most of my team mates can do some PowerShell scripting, but I have some programming classes under my belt.
I have a PowerShell script that is complex enough that I’m confortable calling it a program instead. Roughly half of the code is comments or logging the program flow. Every run generates a step by step log of all actions taken. I have 2 Word documents that summarize the process to different levels of detail, and a fucking flowchart for the visual peeps.
I’m still treated as the only person who could possibly flip the clearly labelled read only and route email to our team only switches and troubleshoot it.
To be fair, I recently learned during a vendor meet and greet that the vendor’s tech guy in the meeting had previously made a consulting firm to sell exactly what I built this program to do. Probably means I’m in the wrong line of work.
I once saw something about how if you are trying to build it yourself instead of using a pre-existing library you come off arrogant.
Can I build it better? Probably not. But do I want to deal with a dependency in my fun side project (unfun), when I could just build it myself (fun)? No.
I probably should to get more practice with it so it is less painful, but…
I feel like these memes have to (mainly) stem from badly documented or broken libraries. The only times where I don’t understand what I’m doing are when I try to figure out what someone else is doing
Same, but past me counts as “someone else”.
The most recent library I wrote for my team at work is painstakingly documented, and everyone has been invited to the multiple recorded training sessions.
They still act like it’s black magic and just push all work and questions to me.
Lol, welcome to the party. I’m not in a programming position, I’m on a systems engineering team. Most of my team mates can do some PowerShell scripting, but I have some programming classes under my belt.
I have a PowerShell script that is complex enough that I’m confortable calling it a program instead. Roughly half of the code is comments or logging the program flow. Every run generates a step by step log of all actions taken. I have 2 Word documents that summarize the process to different levels of detail, and a fucking flowchart for the visual peeps.
I’m still treated as the only person who could possibly flip the clearly labelled read only and route email to our team only switches and troubleshoot it.
To be fair, I recently learned during a vendor meet and greet that the vendor’s tech guy in the meeting had previously made a consulting firm to sell exactly what I built this program to do. Probably means I’m in the wrong line of work.
Dependencies suck
I once saw something about how if you are trying to build it yourself instead of using a pre-existing library you come off arrogant.
Can I build it better? Probably not. But do I want to deal with a dependency in my fun side project (unfun), when I could just build it myself (fun)? No.
I probably should to get more practice with it so it is less painful, but…
Js ?
I also tend to be writing code for embedded systems, so most dependencies are non-starters.