I'm from Aguascalientes, Mexico! now based on New York. Most of my experience is related to code websites and applications, using JavaScript stack-based.
The entire process of development is messy and disgusting and rought with anxiety ridden feelings at each stage. Every success is followed by many other things left undone. One is never finished when one has invented.
With that said, I'd say, it's the middle. That place where you have built something, you committed, and you, even for a moment, lose sight of the end.
Been using UNIX since the late 80s; Linux since the mid-90s; virtualization since the early 2000s and spent the past few years working in the cloud space.
Location
Alexandria, VA, USA
Education
B.S. Psychology from Pennsylvania State University
That so much of my effort is spent doing either of:
Fighting fires - usually resultant of someone else's poor implementation or design or failure to adequately understand the underlying technologies they chose to use
Writing ARRs and "how tos" (that seemingly nobody reads) to try "educate" people so that they don't cause the aforementioned firefighting
Rather than having time to tackle new problems, create new or improve existing architectures/deployments/strategies.
Building things – particularly ones you can point at, with pride, and demonstrate "here's how you can do in a way that is resilient, scalable and sustainable" – is infinitely more satisfying than playing tech-janitor. Conversely, the inability to partake in enough such positive endeavors causes real "am I stagnating" anxiety.
Interviews can get unpleasant and sometimes really feel like an interrogation. But I think I've had enough of them to not care about it to much. As a consultant I'm often for some months to about two years with the same client. When one assignment end and there isn't another one yet I'm getting anxies. I feel kind of stupid about it, cause my salary is fixed anyway. But it's mostly not knowing where I need to be at that time, and the possibility to maybe have to do some work on internal projects, which can be nice, but are often a bit disorganized. Also during such a time there are off course interviews contributing to the anxiety.
The interview process. I don’t know everything all the time. In fact, I take big swings in technology stacks on what seems to be an annual basis. So when a contract role comes up that I’ve used the tech requirements before, but not in months or even years, I have to retrain my brain for that stack, and it never goes well when I cram for an interview in less than 48 hours, or even a week.
I make computers that can see and tinker with electronics.
When I'm not toiling in the digital saltmines I make photographs.
I live on a narrowboat with my partner, 3 cats, and 2 rabbits.
The biggest pain is unnecessary ambiguity. I'm comfortable with not knowing "all of the things" but deliberate obscurity and information hoarding makes me sad.
Web developer at Greggs, UK with a proficiency in VueJS, Tailwind, and Storyblok, as well as other frameworks. I'm also passionate about web design, and mobile app development.
Applying for jobs. I consider myself quite... slow and, as a result, I worry that I will not interview well when asked technical questions on the spot.
Latest comments (63)
Work with IE, it causes too many issues and unnecessary development time.
Tooling constantly letting me down and blocking my progress!!!
On a positive note... finally got a 'Build Succeeded' out of React Native.
all of it. but that's the fun.
The entire process of development is messy and disgusting and rought with anxiety ridden feelings at each stage. Every success is followed by many other things left undone. One is never finished when one has invented.
With that said, I'd say, it's the middle. That place where you have built something, you committed, and you, even for a moment, lose sight of the end.
Being a self-studier, the anxiety that I might be missing out on critical information and having to come up with my own good projects.
Deadlines.
I always seem to overrun! Must be good at procrastinating 😂
That so much of my effort is spent doing either of:
Rather than having time to tackle new problems, create new or improve existing architectures/deployments/strategies.
Building things – particularly ones you can point at, with pride, and demonstrate "here's how you can do in a way that is resilient, scalable and sustainable" – is infinitely more satisfying than playing tech-janitor. Conversely, the inability to partake in enough such positive endeavors causes real "am I stagnating" anxiety.
Interviews can get unpleasant and sometimes really feel like an interrogation. But I think I've had enough of them to not care about it to much. As a consultant I'm often for some months to about two years with the same client. When one assignment end and there isn't another one yet I'm getting anxies. I feel kind of stupid about it, cause my salary is fixed anyway. But it's mostly not knowing where I need to be at that time, and the possibility to maybe have to do some work on internal projects, which can be nice, but are often a bit disorganized. Also during such a time there are off course interviews contributing to the anxiety.
Impractical deadlines
The interview process. I don’t know everything all the time. In fact, I take big swings in technology stacks on what seems to be an annual basis. So when a contract role comes up that I’ve used the tech requirements before, but not in months or even years, I have to retrain my brain for that stack, and it never goes well when I cram for an interview in less than 48 hours, or even a week.
hmmm, for me it has to be dealing with people who rub me the wrong way.
The biggest pain is unnecessary ambiguity. I'm comfortable with not knowing "all of the things" but deliberate obscurity and information hoarding makes me sad.
Watching people consistently not live up to the companies culture, or just straight up act in a way I know for a fact I wouldn’t get away with.
Applying for jobs. I consider myself quite... slow and, as a result, I worry that I will not interview well when asked technical questions on the spot.
Mistakenly pushing to the master branch
Working with people who don't want to learn and improve themselves