- havkom parentSome people that are immune to listen to people with more experience will continue to be ”junior” forever. They may eventually not have the title junior, but they really are.
- Good investigation!
Software developers nowadays barely know about transactions, and definitely not about different transaction models (in my experience). I have even encountered "senior developers" (who are actually so called "CRUD developers"), who are clueless about database transactions.. In reality, transactions and transaction models matter a lot to performance and error free code (at least when you have volumes of traffic and your software solves something non-trivial).
For example: After a lot of analysis, I switched from SQL Server standard Read Committed to Read Committed Snapshot Isolation in a large project - the users could not be happier -> a lot of locking contention has disappeared. No software engineer in that project had any clue of transaction models or locks before I taught them some basics (even though they had used transactions extensively in that project)..
- try catch - where you catch the right types of errors at the right level is hard to beat.
However, many make the mistake to handle any errors at the wrong level. This leads to really buggy and hard to reason about code and in some cases really bad data inconsistency issues.
A rule of thumb is to never catch a specific error which you are not in a good position to handle correctly at that precise level of code. Just let them pass through.
- BTW, I am currently working in an enterprise with a small team mixed with experienced developers (heros - but still always learning because of new complexities) and new developers (heros in becoming).
Absolutely fantastic and we create wonders, but it requires management to acknowledge skill and exceptionalism.
- 6 points
- I agree. The state of level of “basic” knowledge in developers are dropping.
The consequences are that developers can tackle basic tasks which are supported by the frameworks they use, but once something is not supported or straightforward they don’t know what to do and get completely stuck.
From society’s point of view, the usefulness and value of the task force decreases and important problems are not solved or aren’t efficiently solved.
- I think Apple holds developers and third parties to “click through” agreements, so I hope Epic does the same towards Apple (it there has been any breach).
Feels like it is a weak legal argument (even though some jurisdictions may have special “ticket cases” doctrines).
It is not Epics concern if Apple by mistake would enter into a contract with them or not. It is up to Apple to whom they offer such agreements and how.