Home
Starting Up
Case Studies DB
Products
Ideas DB
Vibe Coding Tools
Subscribe to IH+
Starting Up
Case Studies
Ideas DB
Products DB
Sign in
Join
1
Like
6
Comments
What's your worst pain point as a developer?
by
Barakcodes
Hey IH👋,
I mean seriously, what's your worst pain points you'll kill for?
Being afraid of deploy, since it may break something
Making wrong stuff which you're sure you'll need to redo in some period of time
Interesting deploying is a fear for most people. But what exactly do you mean by making wrong stuff which you'll have to redo?
I mean, it's not exactly about programming. Imagine your boss asking you to make some ugly form, with 2384324 fields. And you like 100% sure this is nonsense and soon, after you deploy, he'll check it and ask you to redo this form. So you kind of doing useless things.
This happens all the time, right now I'm rebuilding the whole product, which I did 2 years ago. I always felt like everything's wrong there, and only now the customer understand that this is kind of wrong and we need a new version :)
Wow that's crazy!! Missing the requirements mostly happens when you're not the main decision maker. But I highly advice to start solving the problem first before going off into coding the product. You might find a lot of things that might have been overlooked. I find knowing the reason why they want the software built in the first place and the people who will be using it gives a lot of insight on the software I'm about to build in general.
First, not all developers are guys. If you want to reach out to the community, I recommend being mindful of using inclusive language. Similarly, there are some causes I can - just - imagine killing for, but none of them have anything to do with software!
To your question though, on pain points, here are some:
catching security vulnerabilities, such as SQL-injection attack points
forecasting availability of engineers & designers when life is uncertain (e.g. "if we get the work with client X then Alice and Bob will be busy, but if not they'll be available to work on client Y's project)
making snapshot tests less brittle
curating a shared collection of, say, VSCode plugins that are useful for a specific context (e.g. all of the Vue developers on project Z). Curating, in this context, means selecting, keeping up-to-date and having some sort of consensus process for adding/removing
Thank you for the tip totally overlooked that one. That's great please do share anything you have in mind.
Alright predicting availability of people is really hard I have faced the same challenge once or twice.
Curating a collection of plugins is also irritating since vs code doesn't even keep track of the plugins you've installed.
About the security part of things I have seen some solutions out there which are fairly helpful like synk, I have been using it and it's pretty helpful.