Author here:
Making tech decisions that really take every important financial consideration into account are insanely complex.
I'm writing a book about it for 2 years now, full time, and decided to release the essence of it for free.
This is a prototype application, primarily targeted to software engineers, managers and anyone who runs a software company.
My goal is to offer systemic guidance to tame the complexity of these decisions while also
teaching how the practical side of software development is connected to financial results.
More generally, I would like to help everybody to deliver software that makes more users happy and in turn makes more money.
It's a work in progress, the covered topics are so broad I'm still exploring some of them.
I would be more than happy to receive criticism and feedback about the ideas, mechanisms or any other part of this material.
I'm really glad you liked it! When the strengths of Remix meet your project needs it's an absolute beast! Hope you will have success with it! (Currently I also use Next.js and will stick with it for a while - the next full context review will be about it)
Hey, it's the author here. Thanks for posting the review on HN! It's not getting much traction but I wanted to say, it made my day to see that someone decided it's worth sharing! I put in so much effort into this stuff it means a lot!
Also if anyone wonders, the main benefit of the review is how it tries to objectively lay out the pros and cons of Remix in terms of business impact to help with adoption decisions based on facts instead of hype.
Bash, VIM (without knowing how to exit it). Also I hope some ideas will come into practice from Bret Victor's vision for the future of programming. https://youtu.be/8pTEmbeENF4
I'm also curious to see when will we fully explore the programming language space. I think the possible ways to write code are finite.
Author here. I would like to add some background info. I started to work on this book with a different aim than it ended up pursuing. I originally wanted to train people to become lead frontend developers, but the fist lesson grew into this whole material. I wanted to help answer the question: How to choose the right tools for a given project from a business perspective. I never found any comprehensive guide in this topic. I decided to tackle it and it became much wider in scope then I imagined. Nonetheless I believe it's a valuable topic to explore and this is my attempt on it. It's in early access still around 40% away from completion. I'm really interested in your thoughts!
This is a prototype application, primarily targeted to software engineers, managers and anyone who runs a software company. My goal is to offer systemic guidance to tame the complexity of these decisions while also teaching how the practical side of software development is connected to financial results.
More generally, I would like to help everybody to deliver software that makes more users happy and in turn makes more money. It's a work in progress, the covered topics are so broad I'm still exploring some of them.
I would be more than happy to receive criticism and feedback about the ideas, mechanisms or any other part of this material.