caente

This needs to be highlighted!

This is not a rant, you need to believe in yourself to do art, you need to believe that your work is of the most upmost importance, otherwise you wouldn't be able to give in to it.

The problem is that, from the outside, that is not necessarily true, and often isn't.

I actually agree with the premise, I do need solitude to be creative. I don´t want to feel lonely, but I need to feel that my mind will not be perturbed at unexpected times, for unwelcome reasons. I just want to emphasize that calling ourselves artists is not making us any favors.

it does give me peace, it relaxes me to know my son will have food and shelter. That we'll be able to pay for learning resources and fun things. It helps to know that, if things get a bit rough, we will have some money to hold on until things get better.

It relaxes me to know that if any of us get sick, we'll be able to pay the bills... hopefully.

You two are talking about two different things: - The parent is talking about the ecosystem, how menial tasks have tooling in "less interesting" languages - You are talking about the language itself

I would venture to guess that the parent would agree with you, if talking about the language in a vacuum.

An interesting competition would be to develop a complex product, without external dependencies.

My sad guess is that languages that are filled with escape hatches, like Java, Javascript, or python, would defeat more strict languages.

It's a sad guess, because I actually do prefer the Haskell way.

Interestingly, what made me go through similar evolution was the very language in which I was trying to do all those things, namely Scala. After a few years of trying to be "smart", I realized that the problem was usually bigger than the language.

So perhaps, it wasn't Go, nor Scala, who helped us in our realization, but life and experience?

Interestingly, my case is the exact opposite. When I am coding in Typescript or Python I'm out of place, since I got used to first write the types to make sure everything is aligned, _and then_, start writing logic...

Even in Typescript this workflow is not easy to do, since its compiler is nowhere as powerful.

It could be argued that all engineering problems _are_ economic problems.

> Analysts and project managers might account for technical debt when discussing slipped deadlines.

No they won't, you cannot quantify technical debt, it's a metaphor.

I completely agree with the rest of the post. But "technical debt" is not a cause, nor a valid metaphor to share with management. Other bad metaphors are "building" and "architecture". We are not building anything, we are only writing algorithms that computers will follow. When we write down those algorithms, we are also encoding the inner workings of the company. The true knowledge of how a company works is not only in its documentation or in the heads of their employees, it's also in its automated processes.

The automated processes are the reason why a company can be competitive nowadays. People need to be able to understand those processes, those algorithms, from the code, documentation is never enough, and is never up to date. The code is the primary source of information. If it's not legible, if it becomes arcane knowledge, a black magic that only a consultant can "fix", then the company grinds to a halt, it withers and is crushed by competitors. Be careless about the code quality is not about the suffering of the developers, it means that you are burying vital knowledge of your company, and eventually no employee, no consultant, will be able to dig it out.

If we are trying to figure out how to deal with managers who don't care about the company, but only about absurd deadlines that their managers gave them, then we need to start pushing back, start saying NO. Politics are unavoidable, and often necessary, not all decisions can be made because technical reasons, but we need to start imposing the reality of the code, you cannot rush it, our you are killing yourself.

I'm not saying that experience is worthless, I'll be the first in defending it, but I also know, first hand, that as we get a little older, we get too used to our ways, even if there are others more efficient, that require change.

There is no justification for what they did.

IntellIj has a very nice plug-in, it will tell you a lot about your code, including suggestions of best practices. The down side is that the more "functional" your code gets, the slower IDE becomes(that's also true for Eclipse), but chances are that when that happens, you won't care about having an IDE. So IntellIj will be great to get you started, it does help a LOT.

Is there any difference, on the IDE side, between Scala support and Scala.JS support?

Not sure about this, it seems like you can just code in IntelliJ/Eclipse, but the debugging has to happen in the browser, it does work very nicely(you debug the scala code, not the generated javascript)

I owe you the bonus question :-P

So let's make it the new bottom line. Let's say it is a awful time in history. Internet should be is as ubiquitous as electricity, and electricity should be as ubiquitous as having water near by; but there are places without internet, without electricity and where you need to walk miles to get some water.

I like to think of these time as a new "Dark Ages". We have internet, electricity and infrastructures that would be unthinkable in the actual dark ages, but is far from enough. I like to think about our governments and corporations as the equivalent to those feudal lords and duches and sires. I like to imagine a future that is unthinkable.

Maybe is time to start hoping for a global government, that could be no government at all, but an efficient way to coordinate efforts. Maybe this "global coordination" would be doomed in the event of some global catastrophe that could destroy the necessary infrastructure . It wouldn't matter, if we have it once, we will want it forever. Like with democracy in the greco-roman culture.

This is crazy, far fetched, but so it was the human rights, flying, self moving cars, etc.

We humans are inherently crazy and we like far fetched ideas. We picture an image of the world and then try fit the actual world in it. Some times that takes us to war and genocide, some times to the Moon.

We don’t need to know how this global future will be, we won’t know.

We might start using it right away :-)