"Questions you cannot answer are usually far better for you than answers you cannot question."
- Yuval Noah Harari, 21 Lessons for the 21st Century.
Great read. One of the most clear articulations of the stories (religion, nationalism, liberalism etc.) that have shaped our world.
@katfukui Sorry you had to go through this experience. Wouldn't it help to publish the list of GitHub accounts that trolled you publicly? That way we can report them. Losing all their contributions might teach them that actions have consequences. Their employers also might take notice.
@rbhar90 It's still vendor specific. But you can look into CloudFormation templates and Cloud Development Kit (CDK) for managing AWS infrastructure through code and version control. https://t.co/qYLooDv6XZ
If you like Java, program in Java. If you like C#, program in C#. If you like Ruby, Swift, Dart, Elixr, Elm, C++, Python, or even C; by all means use those languages.
But whatever you do, learn Clojure, and learn it well.
@tommycollison My current recommendations:
1. Sapiens - Yuval Noah Harari
A brief history of humankind
2. Beginning of Infinity - David Deutsch
Explanations that Transform the World
3. Antifragile - Nassim Nicholas Taleb
Things That Gain From Disorder
@tommycollison My current recommendations:
1. Sapiens - Yuval Noah Harari
A brief history of humankind
2. Beginning of Infinity - David Deutsch
Explanations that Transform the World
3. Antifragile - Nassim Nicholas Taleb
Things That Gain From Disorder
"One cannot draw general conclusions from rules of thumb." - David Deutsch, The Beginning of Infinity.
While he talks about this in a specific context, I find we as a society make this mistake all too often. This is especially true of programmers, when it comes to best practices.
@jaseemabid Although not mainstream, a lot of progress has been made in the last few decades on functional, immutable data structures. #Clojure being one of the programming languages to take advantage of these - https://t.co/IfbxDBFzSB
After 3.5 years, finally completed my #OMSCS degree. Got my physical degree certificate over mail recently. I really enjoyed the journey. Learned a lot. Had fun. :)
My experiences - https://t.co/6QgOniwpPD
@GTOMSCS#GTComputing#GoJackets
@skirani This necessitates that they are empathetic. Also, really good engineers are also really good at estimating the time to deliver projects and setting expectations so they don't end up having to work on weekends or late nights.
@skirani I have had the good fortune to work with some great software engineers who are arguably an order of magnitude more productive/performant then the average engineer. However they usually do that by understanding the domain/customer so well that they can simplify complex solutions.
@jose_r_varela@codinghorror Did you mean to say that DRY principle is overrated?
I agree. I find the "Rule of Three" more reasonable when it comes to refactoring: https://t.co/t1wRpYJ5yO
What is the single most important software engineering lesson that you have learned in the course of your career?
For me, it is that "the best code is no code at all". I am constantly amazed how most developers don't really appreciate this.
@codinghorror https://t.co/WWa0fVQ7zX