2,220 karma · joined October 30, 2018
You also have to trust Google to still be operating the service by the time you come to use it.
Ok. That's great. How about the small product companies that have like 20 or 200 engineers as opposed to 2,000 or 20,000?
I have his book Domain Modelling Made Functional as it comes very highly recommended. I haven't gotten to it yet, but I'm even more excited for it now after watching this.
Spin up a Linux VM and get developing?
I do .NET for my $DAYJOB and we use Windows for development. It works, but I wouldn't constrain myself only to Windows for development. I have an Ubuntu VM at home that I do dev in for other stuff.
If you ship a product and I mean like really try to ship it with a launch and everything, you will spend a tonne of time on a) non-technical tasks that don't matter to your day job and b) technical tasks that don't matter to your day job.
For example graphic design, copywriting, marketing etc. All great stuff if you want to go the route of actually trying to launch a company. Terrible to get caught up in if you just want to learn to write production grade systems.
Technical tasks you have to spend time on for stuff you actually will ship do have some value but really it can be limited. You might spend time to build deployment pipelines or auth or HA deployments etc. All of that stuff is great IMHO and I personally value having done a lot of it but to a lot of engineers who work on established code bases and just never ever touch that stuff I feel like it's not a huge value add.
With a project you know you'll never ship you can focus only on the parts you want to. You can then layer lots of little mini-projects into it and use it to try out new things over time.
I guess I'd recommend trying to ship a real project solo at least once too. It gives you perspective.
>All complex systems that work evolved from simpler systems that worked
My definition is of listening comprehension is any information I can glean from listening. Information being a reduction in uncertainty. Doesn't need to be complete. Progress is directional.
I know my language learning algorithm well and I pound it on repeat until my goal is achieved.
I've found close to nothing culturally worthwhile from the mainland.
Edit: actually, now that I think about it... I could never find anything when I was outside the mainland but I went there for a 3 month business trip one time and I signed up to various local services (Spotify / Netflix equivalents) and there f;r the first time I felt I had access to a decent amount of content I enjoyed.
Self studied Japanese to fluency that way. AJATT method but largely concentrated on front loading all the grammar in 4 months then built 10k vocab over the following year. Worked like an absolute charm.
So not true. Maybe depends on the way you study but I focus on listening skills hardcore early on. It's what helps build the natural accent. It's definitely not all or nothing. There are islands of understanding. They tend to grow and grow. It starts out with single words, then grows to two words together then grows to partial sentences and then to full sentences among a paragraph. So on and so forth.
Developers these days say "Chuck it in S3" or "Run it on EC2". I feel they have a strong advantage because they've kind of come to own the language of the cloud.
I've recently gotten a copy of the book Domain Modelling Made Functional. I'm yet to read it, but I'm pretty intrigued by some of what I've seen and I have heard it comes highly recommend.
I'd be very keen to hear of other high quality examples of things people consider good reference material.
The image you linked it interesting. I want to dive more in on the how/specifics. I don't necessarily buy the argument it's trying to make that "just make a function and you no longer have a need for factory pattern". You're trying to accomplish something fairly specific with that. Functions compose, I could see how there are properties they have that can be leveraged to achieve the same goal, but I'm guessing the functions you write or the way you write functions to achieve each of those specific aims likely differ in subtle yet important ways. I'm very interested in those details.
Presumably some of the problems they intend to solve still exist.
Is there some resource you can point to that says in the past when faced with situation X developers tended to use pattern Y, these days that has been superseded with way of doing things Z?
I've seen some of those patterns leveraged to great effect in modern software. But genuinely curious about alternative ways to solve the same problems.
I've definitely noticed the trend towards more and more functional programming these days. I doubt it's simply a case of "just use FP and there are no more problems".