I think you’re being unduly harsh on yourself. At least by the Shopify/COVID example. COVID was a black swan event, which may very well have completely changed the fortunes of companies like Shopify when online commerce surged and became vital to the economy. Shortcomings, mismanagement and bad culture can be completely papered over by growth and revenue.
Right place, right time. It’s too bad you missed out on some good fortune, but it’s a helpful reminder of how much of our paths are governed by luck. Thanks for sharing, and wishing you luck in the future.
That’s what I thought and did this for years. However, the major carriers do offer promotions and incentives that make the phones cheaper, sometimes significantly.
e.g. of recent deal from major US carriers: iPhone 16 deal for $16/month for 36 months ($576 total) versus Apple store $699.
Right, but what does the plan cost? If it’s more expensive than other providers and you are locked in for 36 months, that’s where they make their money.
actually you do need another participant to take the other side of your trade. That’s not a middle man. Market makers, liquidity providers, are a key component of these markets, taking risk with their own capital (no systemic risk, no too big to fail, going to get a government is things go badly), requiring sophistication and specialization to survive in an ultra competitive environment with a high degree of uncertainty and risk exposure.
With all the code syntax highlighting support as a feature, I feel it will become tempting to put code in configuration files (which some of their examples show). That just feels wrong. Code should go in code files/modules/libraries, not mixed with configuration files. If your configuration starts to become code, maybe you need to rethink your software architecture. Or perhaps KSON proves that principle to be too rigid and inferior, and leads to more intelligible, manageable software. I guess we'll have to see.
We agree that there are lots of situations where code ideally does not belong in configuration files, and perhaps if it gets out of hand you need to rethink your software architecture.
However, reality shows that embedded code in configs is already widespread - think SQL queries in dbt, bash scripts in CI/CD configs, or regex patterns in routing rules. These aren't going away. KSON's embed blocks acknowledge this reality while making it safer and more maintainable through proper syntax highlighting, validation, and clear boundaries. We're not encouraging bad practices, we're providing better tooling for existing patterns.
Right place, right time. It’s too bad you missed out on some good fortune, but it’s a helpful reminder of how much of our paths are governed by luck. Thanks for sharing, and wishing you luck in the future.