CEO of Restspace.io, which lets you build and integrate backends with tiny services and no code. Been CTO and developed across the stack at a range of agencies and startups.
I love the go/chess analogy. Particularly because I much prefer go to chess and I much prefer how Cloudflare's offering is structured to AWS. The native territory of Cloudflare, the edge, is a higher level of abstraction than the cloud because you have abstracted away geography and location. On the edge, you simply have to be serverless whereas it's optional in the cloud (think how the internet-native companies for whom the internet was essential took over the space from Microsoft where it was an add-on). You're forced into a more generic model of services because you have less control over the actual hardware on which things run and also because you've abstracted away some of the differences between services that AWS has. And maybe there are just fewer ways to do things that work in a transparently distributed way. Go has that sense of generic pieces over a wide space where there's not much difference between locations, as opposed to Chess where pieces are much more specialised, the space is reduced and the locations are much more important.
CEO of Restspace.io, which lets you build and integrate backends with tiny services and no code. Been CTO and developed across the stack at a range of agencies and startups.
Yeah maybe you have hit on some essential difference of mental attitude and approach which surfaces in both Go/Chess and Cloudflare/AWS. Simple elements complex organisation vs Complex elements simple organisation or something like that. So intriguing. Resonates with the sense I've had increasingly that developers overcomplicate development because of something which is a common psychological motivation. Maybe just that simple things can seem 1. boring and 2. likely to lack capability/power.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I love the go/chess analogy. Particularly because I much prefer go to chess and I much prefer how Cloudflare's offering is structured to AWS. The native territory of Cloudflare, the edge, is a higher level of abstraction than the cloud because you have abstracted away geography and location. On the edge, you simply have to be serverless whereas it's optional in the cloud (think how the internet-native companies for whom the internet was essential took over the space from Microsoft where it was an add-on). You're forced into a more generic model of services because you have less control over the actual hardware on which things run and also because you've abstracted away some of the differences between services that AWS has. And maybe there are just fewer ways to do things that work in a transparently distributed way. Go has that sense of generic pieces over a wide space where there's not much difference between locations, as opposed to Chess where pieces are much more specialised, the space is reduced and the locations are much more important.
yup! i was pretty happy with the analogy when i thought of it haha
Yeah maybe you have hit on some essential difference of mental attitude and approach which surfaces in both Go/Chess and Cloudflare/AWS. Simple elements complex organisation vs Complex elements simple organisation or something like that. So intriguing. Resonates with the sense I've had increasingly that developers overcomplicate development because of something which is a common psychological motivation. Maybe just that simple things can seem 1. boring and 2. likely to lack capability/power.