This is an interesting way of breaking down developer types. I would definitely say that I'm more of a "guard" type. It frustrates me to no end when setting up an environment requires excessive...
This is an interesting way of breaking down developer types.
I would definitely say that I'm more of a "guard" type. It frustrates me to no end when setting up an environment requires excessive manual tinkering of settings and configuration, or when deploying code requires a lot of manually moving directories around and creating symlinks. It especially frustrates me if code is written in such a way that I'm spending upwards of an hour trying to figure out how the hell my data is traversing through the business logic of a system when it should only take me about five minutes when written in a way that isn't a convoluted mess.
I would rather spend a few hours writing some code in a way that allows me to spend only a few minutes making changes later on as opposed to spending only a few minutes writing some code in a way that forces me to spend a few hours making changes to it later. Likewise, I would rather spend a few hours writing a proper environment provisioning script so I can rebuild my dev environment as frequently as I want to in a matter of minutes without even having to think about it instead of manually setting it up every single time something breaks and forgetting about some configuration change in the process.
I'm a starter. Unfortunately, I have to work really hard at finishing things. I'm the Architect at &yet, and that's really my strength -- making a plan, building skeleton/tracer of what I think it...
I'm a starter. Unfortunately, I have to work really hard at finishing things. I'm the Architect at &yet, and that's really my strength -- making a plan, building skeleton/tracer of what I think it should be, and enabling others to make it happen. There are other sub-types of starters too, but I don't think that's as interesting to talk about because finishers are generally under-valued and often flat out filtered out of the hiring process.
A friend of mine started a rust gameboy emulator. That sounds like a fun way to dive into a new language (but a lot of work). Generally I find something that is painful in other languages but this...
A friend of mine started a rust gameboy emulator. That sounds like a fun way to dive into a new language (but a lot of work). Generally I find something that is painful in other languages but this language promises to make better. Every language tends to claim their purpose for some type of problem.
First dates are important! Need to ensure that you impress your 1 line program. Make sure you wine and dine it so that there is less chance for bugs in future releases.
First dates are important! Need to ensure that you impress your 1 line program. Make sure you wine and dine it so that there is less chance for bugs in future releases.
This is an interesting way of breaking down developer types.
I would definitely say that I'm more of a "guard" type. It frustrates me to no end when setting up an environment requires excessive manual tinkering of settings and configuration, or when deploying code requires a lot of manually moving directories around and creating symlinks. It especially frustrates me if code is written in such a way that I'm spending upwards of an hour trying to figure out how the hell my data is traversing through the business logic of a system when it should only take me about five minutes when written in a way that isn't a convoluted mess.
I would rather spend a few hours writing some code in a way that allows me to spend only a few minutes making changes later on as opposed to spending only a few minutes writing some code in a way that forces me to spend a few hours making changes to it later. Likewise, I would rather spend a few hours writing a proper environment provisioning script so I can rebuild my dev environment as frequently as I want to in a matter of minutes without even having to think about it instead of manually setting it up every single time something breaks and forgetting about some configuration change in the process.
OP, what kind of programmer would you say you are?
I'm a starter. Unfortunately, I have to work really hard at finishing things. I'm the Architect at &yet, and that's really my strength -- making a plan, building skeleton/tracer of what I think it should be, and enabling others to make it happen. There are other sub-types of starters too, but I don't think that's as interesting to talk about because finishers are generally under-valued and often flat out filtered out of the hiring process.
OP, when writing your first Hello World program in a new programming language, where would you take it out for dinner?
Well, it used to be Costco, but they got rid of their Polish dogs. I'll have to come up with some place new.
A friend of mine started a rust gameboy emulator. That sounds like a fun way to dive into a new language (but a lot of work). Generally I find something that is painful in other languages but this language promises to make better. Every language tends to claim their purpose for some type of problem.
First dates are important! Need to ensure that you impress your 1 line program. Make sure you wine and dine it so that there is less chance for bugs in future releases.