718 karma · joined June 28, 2007
Different strokes for different folks.
https://pragprog.com/book/swdddf/domain-modeling-made-functi...
This is parroting anti-intellectual nonsense.
Needless distinctions like that make the fresh air a little less fresh...
http://spodekacademy.com/wp-content/uploads/spodekacademy-co...
Point taken about active malice... but I've also seen companies with mostly in-house code cover up instances of rootkits on production servers and malfeasance related to credit cards.
I'd rather companies use third party open source crypto, for instance, even if it sometimes gets compromised, because it's a lot more likely to come to light.
If you're trying to talk about hiring for full time employment as opposed to contract work... what happens there is as long as people are able to get through whatever idiosyncratic hazing process was involved in hiring, they're going to be at the company for at least a year. It's perceived as hard / risky to fire people, even if they can't program their way out of a wet paper bag.
This stuff happens all the time, it's not that different from evaluation and use of third party code. "This project has 500 stars on github, it must be good." "This guy used to work for Google, he must be good." Now you're stuck.
CEOs outsource critical things without meaningful oversight all the time.
Kotlin checks exhaustivity of when only if it is used as an expression, not as a statement.
https://kotlinlang.org/docs/reference/control-flow.html#when...
Kotlin doesn't allow destructuring in when:
https://discuss.kotlinlang.org/t/destructuring-in-when/2391
This is just straight up weak coming from any reasonable ML derived language with real pattern matching.
How is this more powerful than rust match?
I've had roles where I changed ~5 lines of code that resulted in at least my yearly salary worth of reduced operating costs. Programming can be a high-leverage activity, FAANG salaries aren't necessarily irrational.
Sestoft is a very clear writer, and F# is a better language than most for writing interpreters or compilers.
Software engineer and senior software engineer are 100k+, among many others.
Read Odersky's book, write code, still have access to all JVM libraries and a lot less brain damage.
There are people that try to write worse Haskell in everything from Perl to Kotlin too. The reputation is overblown and has little to do with the actual language.
Scala is still the least-bad option for a JVM language.
Anyone who can't be productive in Scala (not "better java", not "worse haskell", Scala) isn't someone you want on your team anyway.
Rust is very clearly an ML derivative, not (just) a better C++