This is just not true. The Lisp family contains all conceivable variants of languages, from statically typed Coalton, to dynamically typed Scheme. From functional, immutable by default Clojure to the imperative-style of Common Lisp.
There are prologs, constraint solvers, ffis, JavaScript alternatives, garbage collected and not garbage collected languages that call themselves lisps.
I've seen a few of your comments here today, and generally speaking they are appeals to authority, ad-hominem attacks dressed in allusions to superiority in either knowledge or manners, and truisms without substance. In a manner of speaking: bait. So I guess I'm probably unsurprised if your experience of this is people seeming disagreeble towards you.
I wouldn't argue about things that are a matter of taste normally, except that I've had the experience where I've turned down optimizer settings in order to debug some code better and then the had stack overflow.
Sigh and yet it continues to be true. You can make a pragmatic decision and rely on tail call optimisation for your specific case, but if you are writing a CL library, then it is not idiomatic to use recursion in the same way that you would for Clojure or Scheme.
Even with SBCL, for example, it doesn't have tail-call optimisation for all architectures at all optimisation levels.
Senior Engineer means many different things, even within the same company. It could mean, "This person is more productive than everybody else around them" or it could mean, "This person isn't that great at software development but they know some product area so deeply that it would be too expensive to replace them."
First of all, congratulations. As somebody that also achieved the senior developer title within the first three years of being hired out of University, mostly by luck: Yay money, but I wasn't a senior engineer really for another five years. For me, I needed to see the long term effects of the changes that I'd made and the software I had written to really understand the difference between cargo cult behaviour and what really mattered for the business I was working for.
If you don't have personal examples of using a profiler to diagnose an issue like "too many round trips" and identify where those round trips are coming from, then you've never inherited a complex performance problem before.
I agree with this article fully, but there is a problem that most blog posts about identity don't talk about before telling you what do with your own. What is identity actually for? This is the only article I know of that talks about this:
I mean if it didn't make the gambling organizations more money they wouldn't do it. Gambling industry has always been about how much wealth it can extract from the punters without being regulated for it.
Hopefully this research ends up being used to justify more gambling regulations, but governments are addicted to the gambling lobby donations so who knows what will happen.
I don't think we can know whether or not this is the case in our own lifetimes, because we are so immersed in popular culture that we can't be objective about it. Enough of our historical great composers weren't venerated until after their deaths, and to describe composers as "hiding" within the most popular media of our era is a great disservice to the many composers that don't have the fame, connections and reputation to be hired to write for these.
I would also point out that composing for a medium like a game or a movie places a great deal of constraints upon the composer, in terms of theme, cost of instrumentation, duration and most importantly: what is safe and palatable for an executive to approve of.
The distinction does matter, because by not wearing a mask, instead of indicating that you don't care about your own safety, you're indicating that you don't care about anybody else's.