As a Dev, what is a pain in the a** for you?
Trying to generate some blog post ideas. What is something that is a pain in the a** for you that you as a dev?
IE deployments, hosting, vs code setups, programming concepts, frameworks, etc...
Trying to generate some blog post ideas. What is something that is a pain in the a** for you that you as a dev?
IE deployments, hosting, vs code setups, programming concepts, frameworks, etc...
The biggest pain for me are the things that just should work at the first try. For example:
This two should just be painless, instead they hopelessly drift to a huge blood bath, every time.
And because they add no value to the business, it's always a stressful nightmare.
Same here. I wish I could - just - deploy - a container. Allow for it to autoscale to zero or up. And none of that k8s complexity and cost when I don't need it. I don't want to deal with the horrible UX of either AWS or Google Cloud. And I want also have the options to run on Hetzner or Digital Ocean - just to have options.
What you are looking for already exists in the form of CaaS ( container as a service) on both AWS ( App Runner ) and GCP ( Cloud Run).
Well, maybe for a single container. I guess the closest of what I have in mind is AWS ECS. But again both consoles (AWS+GCP) are horrific. I guess one could try AWS ECS via Terraform. But I also have projects were AWS/GCP/Azure isn't really an option.
It still feels like there is much room for improvements in this space.
Shameless plug (but hey, it's indiehackers!) – That's exactly why we're building: encore.dev
Interesting project - but seems to have a different focus.
Which clouds? I’ve used quite a few but I find Heroku to be the best and easiest to setup.
The Big3 are brutal, because they forcus on huge enterprise customers, leaving dx experience far behind
100% agree - the big 3 are fine being the lowest infrastructure level of the internet and having other services with better UX resell (see: Netlify functions running on AWS Lambda).
Anything that can be serverless, will be serverless eventually which will make it easier for devs, but there's still a lot to be done with building good abstractions for serverless systems (DBs, functions, caches, etc.)
When somebody says they need to hire a full-stack developer and ask if I'll trade services/royalties for a really bad app idea.
Been working in EC2 ubuntu its been a month now. Currently I'm maintaining and deploying a flask python RestfulAPI for my new startup! The pain is when I get indentation error, the gunicorn service fails to restart due to that and yes even after checking multiple times I can't any bad indentations and sonetimes it is fixed after I switch from vim to nano or vice-versa, absolutely pissing. By the way welcome to programming!
Hey use this https://github.com/psf/black
You probably either want an IDE (VSCode, PyCharm, etc..) or add plugins to Vim to help you catch those issues earlier in your development process. Aside from that, some simple smoke tests can help: just call the core endpoints before in the dev server before pushing to prod to make sure everything returns as expected.
Yup made a script to run a bunch of commands where at first I format the src first and in my case I dont have to call the endpoints I can simply check the status of the service in my case gunicorn.
Being a dev.
It stops me from feeling bad if I try to sell my product and not build new features.
React did it, Firebase did it, .NET has done
it for years. Major API changes! Which means all “old” StackOverflow answers it even
new ones about old versions are misleading. Often the documentation can be confusing as
a result.
But the crown prize for this problem has to go
to NodeJS and Webpack and the JS ecosystem with its myriad module systems.
Keeping libraries and frameworks up to date. I’m using React Native and have been meaning to look into tools like rnx-kit, but haven’t gotten around to trying it out yet. Overall, this is my biggest dev pain point.
Interesting. So are you afraid to yolo update your libraries and if something breaks you have to spend a bunch of time fixing things? Or is there complexity to updating react native libraries? I've never built anything with it but I always assumed it used npm/yarn.
Not so much afraid, but I’ve more or less bricked my project twice before by attempting major version updates to React Native and other libraries like Firebase, so I now associate very high cognitive load with those updates and put them off until I know I have a decent enough chunk of time to work through any issues. In general, I also get overwhelmed at keeping up with the speed of updates across various libraries.
This comment was deleted 4 years ago