32,006 karma · joined July 21, 2008
And this is exactly what a problem is with the concept of "generations": they only work as far as they take into account geographical circumstances in different parts of the world. For example, a generation who lived through the 90s in the USA and Western Europe will have a very different experience from the same one in the Eastern Europe, especially the Balkans.
But this whole topic raises an important question: is there any way to check whether someone is a slow thinker, e.g. when interviewing people for work? It would be great if one could easily determine if someone doesn't have the required knowledge or is simply slow to formulate the answers.
Yes, you got this very wrong. Yes, whitespace is significant in Python, but it can be either tabs or spaces, as long as it's consistent; although PEP8 [0] recommends using 4 spaces per level of indentation.
It's hard to tell what your issue with backward compatibility was exactly without examples. You are not wrong, Python does occasionally introduces backward incompatible changes - but in most cases they follow a clear deprecation process, announcing a change long before it is eventually introduced.
King Street in Hammersmith, London, was named after John King, Bishop of London in 17th century. [0]
Neanderthals were named after Joachim Neumann, a 17th century clergyman and composer who Latinised his surname to Neander (both literally meaning "new man"). He particularly loved a certain valley near Düsseldorf, so much in fact that it was renamed "Neandert(h)al" after him. [1]
Sideburns, a once popular style of male facial hair, was named after the Union general Ambrose Burnside. [2]
[0] https://en.wikipedia.org/wiki/John_King_(bishop_of_London)
:shut-up-and-take-my-money.gif:
Note that this is not the same concept as an optional argument, which is one that has a default.
[0] https://docs.python.org/3.11/library/stdtypes.html#types-uni...[1] https://docs.python.org/3.11/library/typing.html#typing.Opti...
I have long been arguing that this is exactly what "readability" means. Readability is completely subjective, and depends on personal experience with various languages, types of syntax and so on.
1. T | None
2. SuccessT | FailureTJust the third child, or any after the second? If the latter, I would assume it's an incentive to have more children.
That being said, while I understand their choice of using Pydantic for defining the schemas, I believe they should integrate a more platform independent standard as a first-class citizen -- something like JSON Schema, or even protobufs (or both).
Essentially the latter; what you thought will be 90% the time ends up being just the first 10%. And the rest is spent on the 10% of the code, plus everything else that is part of the project besides the code: reviews, testing, revisions, deployment issues etc.
This is not correct. It is well known that the first 90% of the code takes the first 90% of the time, and the remaining 10% of the code takes the other 90% of the time. [0]
[0] https://en.wikipedia.org/wiki/Ninety%E2%80%93ninety_rule
It usually starts when a team is quite small, and someone builds some DevOps pipelines that nicely automate deployment to dev and test environments. When it comes to production deployment, it seems natural to simply duplicate the same pipelines -- however, production is generally quite different from other environments:
1. There is an approval process, which does not exist for other environments. Even if it is possible to have it fully automated (I have yet to see it in practice), it requires rigorous tests and verification of the code; and if it is not automated, the process generally involves plenty of back and forth communication between testers, product owners, developers etc.
2. Ideally, deploying to production should not involve rebuilding the project anew. Once you deploy it to a testing environment, and it passes all the tests, deploying the exact same artifact (docker image, ZIP file, Python wheel, binary executable or whatever) to production is the only way to ensure that you're deploying what has been tested and approved.
I have searched for a third-party tool to manage this process, but haven't found anything satisfactory yet (suggestions welcome!) -- one of the reasons is probably the fact that the processes differ so wildly between companies and teams.