Why invent a new file format when there is https://jsonresume.org/? Its also quite easy to customize and add more things as it does not prohibit extra values
Yes, exactly this! We are actually spending soo much time deriving, thinking, formulating & refining OKRs from roadmap items that we could just declare as simple "Goals". We could get so much shit done during that time.
Most of the time as the quarter goes on, we then scrap those OKRs anyway because we didn't manage to do them or they were too specific and requirements changed.
I always had the feeling that what we are doing is bullshit. So great to finally hear it from someone else.
I wonder how many engineering companies actually use OKRs though.
Yeah I thought sth like this is possible, but (correct me if I'm wrong) this (ab)uses the ELF header and punts data in there, which goes against my requirement
> It should be a ‘proper‘ executable binary according to the spec
Thanks, that makes total sense. I was so focused on the ELF part that I didn't even consider optimizing the initial assembly further. Will fix it and edit the article.
There are actually IDE plugins which perform 'semantic line wrapping'.
But that is besides the point. Of course, it can make sense to add manual line wraps, especially if the developer intends to make his intentions clearer by using line breaks at specific points.
But lots of developers use formatting plugins to force line breaks anyways - and they are no better then the IDE linewrapping.
And I want it to be able to handle lots of connections. One server might not be enough, so it needs to scale. The process could also take a while, so I need a queue. Yeah I could setup, AWS API Gateway, SQS, ECS with Autoscaling etc. But that's a lot of boilerplate.
meet.hn/city/de-Munich
Socials:
- https://github.com/michidk/
- https://www.linkedin.com/in/michael-lohr/
- https://x.com/miichidk/
Interests:
Cloud, Entrepreneurship, IoT, Open Source, Programming, Startups, Web Development, Freelancing