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!
Other Media
Feel free to reach out to me in other media!
Oldest comments (69)
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.
Bad leadership is the worst, I've worked with some of the best managers and the worst. The worst would do things like micromanagement, placing themselves as unnecessary dependency, trying to portray my desings as theirs, the list goes on and on :|
Software still is mostly about people. Bad People = Bad Software.
Yup, management that gets in the way of the development process is just the worst.
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.
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
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!
I resemble that remark... (shame of junior dev)
What? Like this?
delete databasePtr;
?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.
Oh for sure. I do the same thing. Delegate the scary stuff to my betters.
Debts
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!
A self-taught guy has to pay rent and foods too. 😭
Ya but it's a lot lower cost than going to college
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.
Logs. This is why you always keep plenty of debug info handy.
It really pays off to record the conditions of the program in-case a bug occurs.
Yeah I make sure to keep printing the stack trace all of the time especially when I'm still in the development process.
Debugger is also great!
Production bugs that result in data not being saved.
Similar to production bugs where data gets changed unintentionally and/or deleted!
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.
3. happened to me not too long ago; then I did a benchmark and my code was x10 more performant sooo... not a complete waste of time, at least :D
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
Ya, but that's just the nature of software development no?
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.
Developers/teams who choose technologies purely on whether they're popular, with no regard to the appropriateness to their project
Typescript cough cough
I stopped arguing with those people, and I just link them to this article.
React also
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)?
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 😞)
Oh, yeah! Vanilla Javascript/HTML/CSS would perform better than React for simple noninteractive webpages. It also has better SEO.
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
honestly very relatable lol
1) Core dump segment fault lol
2) Index out of range
3) Explaining someone what i am doing
1) Core dump segment fault lol
2) Index out of range
3) Explaining someone what i am doing