Interesting. I prefer working on smaller projects where I do the entire thing myself from start to finish. This is mostly because I don’t particularly enjoy familiarizing myself with somebody else’s code. Although if I get stuck I will ask my fellow devs for input, and I enjoy showing them whatever cool thing I did once it’s polished.
At my current workplace I fill the role of ad hoc programmer, where I’m the guy to ask if somebody needs some small tedious thing automated or parsed I’m the one who can get it done quickly.
I also don’t prefer making software intended for other people to use. If something is a background data monitor or something it doesn’t need a shiny intuitive UI or anything like that. I just need to write it and set it up to run every x days or whatever. If people besides me and other devs will need to use something, that adds an entire layer of tedium in the form of usage guides and more exhaustive (layperson friendly) documentation.
Interesting. I prefer working on smaller projects where I do the entire thing myself from start to finish. This is mostly because I don’t particularly enjoy familiarizing myself with somebody else’s code.
Although if I get stuck I will ask my fellow devs for input, and I enjoy showing them whatever cool thing I did once it’s polished.
At my current workplace I fill the role of ad hoc programmer, where I’m the guy to ask if somebody needs some small tedious thing automated or parsed I’m the one who can get it done quickly.
I also don’t prefer making software intended for other people to use. If something is a background data monitor or something it doesn’t need a shiny intuitive UI or anything like that. I just need to write it and set it up to run every x days or whatever. If people besides me and other devs will need to use something, that adds an entire layer of tedium in the form of usage guides and more exhaustive (layperson friendly) documentation.