11–20 of 23 posts
What is this ecosystem where you can declaratively specify your program in YAML? And what are these magical dependencies that let you do this? Is it specific to an industry vertical? Could it be replicated for others?
If there is such a capability, I'd want to get in the business of making the tools rather than the apps.
Let me guess your packages aren’t up to date either and no one checks if they’re maintained?
Tell your manager when there are no challenges in the job the most skilled people will leave.
> all I do is edit YAML files (I don't work in DevOps, it's not k8s) and write glue for code that I'm not allowed to write myself What is this ecosystem where you can declaratively specify your program in YAML? And what are these magical dependencies that let you do this? Is it specific to an industry vertical? Could it be replicated for others? If there is such a capability, I'd want to get in the business of making…
> all I do is edit YAML files (I don't work in DevOps, it's not k8s) and write glue for code that I'm not allowed to write myself What is this ecosystem where you can declaratively specify your program in YAML? And what are these magical dependencies that let you do this? Is it specific to an industry vertical? Could it be replicated for others? If there is such a capability, I'd want to get in the business of making…
> I've had entire weeks at work where all I do is edit YAML files
Editing config files isn't what I do every day, it's just an example of the consequence of using multiple massive frameworks combined with hundreds of libraries. So much work is done for you that at times you just need to configure everything.
I would say the combination of cloud services and open source means there is no better time to be a developer. You can get things done as a solo developer that would have been impossible 20 years ago: not having to fret over backups and OS versions because your cloud vendor does it in a serverless system is a massive time saver by itself.
If you're struggling to compete with open source packages when you write code, it's a good sign you are writing the wrong code.
It should be obvious though that the very best systems are always boring to work on. The vast majority of software does boring things (ETL or CRUD or security stuff) and there is no way to make it exciting. There is plenty of satisfaction in making it reliable though. Not everyone can work on the exciting stuff, not everyone is suited to working on the exciting stuff either.
I feel like this but with cloud services (AWS, Azure) instead of Open Source. They have solved most problems, are cost efficient and easily get buy in from upper management. Developers jobs are then to write configuration and plug things together. Very boring stuff!
> all I do is edit YAML files (I don't work in DevOps, it's not k8s) and write glue for code that I'm not allowed to write myself What is this ecosystem where you can declaratively specify your program in YAML? And what are these magical dependencies that let you do this? Is it specific to an industry vertical? Could it be replicated for others? If there is such a capability, I'd want to get in the business of making…
AWS Cloudformation templates with pre-defined lambdas for example.