Of course, types alone can't represent every error cases out there (especially the one related to number or string), so I still write Unit Test for those cases. But the number of Unit Tests needed is much lower.
559 karma · joined January 25, 2017
Of course, types alone can't represent every error cases out there (especially the one related to number or string), so I still write Unit Test for those cases. But the number of Unit Tests needed is much lower.
[Added] Of course writing webpages pays well enough, but I still can't shake off this feeling that I am missing something by not jumping on the AI/ML train though.
I think the section about Zen and Analytic thinking helps shaped my way of thinking. Before that I just charged blindly into problems, only to get stuck somewhere. But after reading the guide, I often stop for a while, thinking 'why doesn't this work?' and try to figure out how, back gathering all the evidences and make a mental model of it in my brain. Interestingly it is quite useful for programming too.
I guess it's fine to hate your government, but a better solution is to change it than avoid paying tax. Because if people pay less tax then then the poor and vulnerable will be affected first, not the corrupted interest group.
Okay, I understand that it breaks systems with badly written audio drivers, but can we really blame Pulseaudio for that?
Wikipedia has something interesting about VX:
> VX can also be delivered in binary chemical weapons which mix in-flight to form the agent prior to release. Binary VX is referred to as VX2,[6] and is created by mixing O-(2-diisopropylaminoethyl) O′-ethyl methylphosphonite (Agent QL) with elemental sulfur (Agent NE) as is done in the Bigeye aerial chemical bomb.
So maybe two of them were holding different component and they only reacted after being sprayed on Kim's face. If this is true then this is a very intricate assassination plan.
I don't know about America but here repairing expensive machinery is the job of engineers, not factory worker. The latter's work involve pushing button, soldering, assembling etc.. but not something that require critical thinking or problem solving. Automation is still either 1. more expensive than manual worker (in case of FMS) or 2. only applicable for large scale/high value added manufacturing.
FMS: Flexible Manufacturing System.
> If I encourage collaboration between technical and domain experts and work iteratively to refine a conceptual model, I can claim I’m doing DDD.
This. I am tired of the so-called 'DDD-experts' trying to convince us that you must use X framework with Y techniques to 'properly' implement DDD. In the eyes of some managers I know DDD is something mysterious, something that requires expert consultants to do and if we copy paste their design we will be doing 'DDD'. That explains why in my company each team has their own understanding of 'DDD'. To me, the Ubiquitous Language is the essence of DDD. As long as I name my class/method/function/variable accordingly then I am doing DDD. And we try to make it so that the Domain Experts can read our code and say its business logic is correct or not, even if they don't know anything about programming at all. To do that we can use whatever tools/languages we want, OOP, FP, Free Applicative, DSL etc..
It's the Domain that matters in Domain Driven Design, not the framework or languages or even design patterns.
EDIT: Fixing formatting again..
- As for slow compilation times, incremental building helps a lot.
- Intellij works most of the time, and if it doesn't a few type annotation will fix it.
- It's very hard to find people with Scala experience. We have given up on finding those and decide to train people from the beginning for 2 months. I myself studied mechanical engineering in university and I can code just fine after a few months.
- The language itself is very complex, so we let more experienced programmers write the backbone/framework/library/common parts and the less experienced one do the code glueing-job. That way we can have Scala type safety and expressiveness without scaring the juniors. IIRC one company used Haskell also do the same and they said it is very hard to introduce runtime bugs because almost everything were caught during compile time, "If it compiles, it works".
You may ask why going through so much trouble just to use Scala. There are many reasons (speed, type safety etc..), one of them is that we can be immensely productive when needed, the conciseness of the language combine with a powerful type system let us implement complicated features rapidly without very few bugs. IMHO Scala strives to combine both FP and OOP on top of JVM so a lot of tradeoffs had to be made. The developers have to learn a lot of concepts and have good self discipline, but in exchange we can write fast, robust systems and even enjoy it.
(Edited for better formatting, this is my first time posting here.)