What are the things that scare you as a Developer?
source link: https://dev.to/rammina/what-are-the-things-that-scare-you-as-a-developer-3gkd
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
Posted on Oct 31
What are the things that scare you as a Developer?
Happy Halloween, everyone!
I think the question fits the theme, so I'd like to ask everyone:
What are your fears as a developer?
Here are the things I'm scared of (reasonable or not aside):
- not being able to find my next freelance client.
- production bugs.
- performance anxiety when showing interviewers and clients my work output.
- Imposter Syndrome (fear of being a fake or being too dumb)
that my Imposter Syndrome isn't even real, and that I actually suck.
running into a bug that has no StackOverflow, Github issues, and/or online solutions (which means I need to figure it out on my own).
posting a question online (especially on SO) where others might judge me.
the feeling of I'm not improving enough (lack of visible progress).
Almost forgot to add:
- not understanding what I'm reading
I'd like to know what you all are afraid of as fellow developers!
Note: I'm learning a lot from what everyone's sharing. Thank you, everyone!
Discussion (32)
Developers that choose technologies purely on whether they're popular, with no regard ro the appropriateness to their project
Typescript cough cough
I stopped arguing with those people, and I just link them to this article.
React also
Thread
Thread
React?
As someone who really loves React, I got hit pretty hard by that! Haha. When would React be inappropriate for a project (assuming its still FE web development)?
Thread
Thread
Many, many places. Maybe not just React, but frameworks in general. I've lost count of the number of REALLY simple websites (Portfolio websites with next to zero interactivity, holding pages for upcoming projects, single page form websites, etc. - the list is long) that, for some bizarre reason, have been built using a framework. It literally makes no sense
(I personally loathe React, that's probably why I singled it out initially. I work with it on daily basis though, unfortunately 😞)
Thread
Thread
Oh, yeah! Vanilla Javascript/HTML/CSS would perform better than React for simple noninteractive webpages. It also has better SEO.
Thread
Thread
Vanilla JS would perform better than React for ALL websites. Frameworks become handy when the complexity of the site means that development using raw JS would start becoming a nightmare... in these cases, a framework would likely be easier to manage. It's a trade-off
CollapseExpand
Nothing is more scary then manually running a delete statement on a production database. 😳
Everyone, got that one story...
I think that is one common fear among many developers haha!
CollapseExpand
Sinking deeper and and deeper into a given problem asking all the while if there is in fact light at the end of the tunnel, egged on by solid estimation in the first instance, then hope then the sunk costs so far, and ever fearful that it may be ... a dead end.
Frustratingly poorly documented libraries that you pretty much, or totally have to reverse engineer while trying to utilise them
Spending a long time developing something only to find someone else did it better and faster and you can toss the fruits of your labor out the window and just use that.
Dealing with irascible hubris and poor interaction skills in other developers, not least gate keepers on repos or fora.
Forking frigging forking ... umpteen wasted effort solutions solving the same problem, meaning when you want that problem solved, you don't have two or three options (which would rock) but like 20 or 30 and your first job is endless pros/cons research before committing to a path.
I see! I've dealt with number 2 and 3 quite a few times before. 4 seems like it's very common in the corporate world.
CollapseExpand
Nothing's quite as scary as bugs that seem to have fixed themselves without any human intervention.
Except maybe the idea that I / we might do something with our tech that ends up hurting people. :(
Oh, and user tests are terrifying every. single. time.
Ah, I have encountered this multiple times and it is definitely scary when the code you're writing is for other people.
I didn't mind it as much when I was just doing personal projects.
CollapseExpand
I'm scared of one particular situation. It goes a little bit like...
Project manager: Hey. Do you remember that api you did for that presentation a few days?
Me: yeah... that thing that is totally still under development.
Project manager: That one. It's in production now. We need you to fix it.
Me: I'm sorry-- what now?
Yikes, who would push code that is still not tested and hasn't gone through quality assurance to production?
Then again looks at many companies
CollapseExpand
not really as a developer, but as a citizen, I cant' see really where technological intelligence is leading us too. I see so much confidence on it and this is not good. Also so much centralized and becoming so much high level intelligence, meaning the gap between people knowing the smallest building blocks and also theory empowering bigger tools are so few in this world. Really scary. What's the solution ? we must slow down. How ? giving less power to big brothers and being independent or at least capable of being independent from technology. One would say, but hey television and telephone were the same, I think not. Must engineers graduating from universities at that time knew how these work at the lowest levels. Not anymore ! Facebook, Google ... are the only ones knowing how their products are built. So frightening to me.
There are open source technologies (and projects) around though, other fields have more centralized knowledge than development.
Like, anyone could learn programming if they just look around for the right resources and people.
CollapseExpand
imposter syndrome is also a big one for me. i'm also terrified that low code development will get so advanced that the need for developers is going to significantly decrease
I think there will always be a need for developers, that's just my opinion.
People with high self-awareness and low self-esteem will most likely have Imposter Syndrome. Also because the field of programming requires a lot of self studying, it's a lot harder to get validation about your skills.
CollapseExpand
most of what you said and...
micromanagement, jerk coach/pm, doing all the work in team, bad company..
I mean no offense, but it seems like you've went through tough times. Those are also the reasons why I don't want to work for a corporate environment.
CollapseExpand
CollapseExpand
There is also self learning? You can do it without going to university/college or boot camps. It's a lot harder, but it's definitely possible!
CollapseExpand
Not an issue with every application, but I am terrified of revealing client PHI/PII.
As a freelancer, I'm also scared of this because of the legal consequences. I try my best to use cloud-based solutions for security of data to avoid the responsibility of doing it myself.
CollapseExpand
Production bugs that result in data not being saved.
Similar to production bugs where data gets changed unintentionally and/or deleted!
CollapseExpand
What are your fears as a developer? changes.
The constant updating of technologies? The fact that you always have to learn for the rest of your career?
The requirement changes after all old requirements are already implemented xD
CollapseExpand
My own code scares me. So does internet explorer.
CollapseExpand
honestly very relatable lol
Recommend
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK