erokar

You'll spread yourself too thin as a developer if you need to do a lot of ops too. Specialisation is a good thing.

You don't want a doctor who brags that she can do heart surgery, perform talk therapy and treat your skin rash. You want someone how knows a lot about your specific problem because she's prioritised it over other things.

Forget about the 10k myth. I think it's absolutely feasible to switch careers at your age, and I assume it's software development you're thinking of. I think half a year to a year of intense study and practice should be enough to make you employable.

But first, figure out if this is something you would like doing. Take a course like e.g. this https://www.coursera.org/learn/python for a month (you can audit it for free) and see if you actually like programming. If you do, carry on.

I agree. While it certainly contains good writing that book is also mannered and sentimental, my least favourite of his.

> I think people are very slowly coming to the realization that all the free love stuff didn't really make their prospects of a good family better, and after all, for the most part that is our biological drive.

There's no evidence of any biological drive for family life or having children. (There's a cultural norm for it, for sure.) There's a biological drive for sex, and that's all evolution needs to keep it going.

Sure you can — in your own code. But everywhere else inheritance is a virus. Spring, Rails, .NET Core, Django, Pydantic — just to take some random examples are all fundamentally base on inheritance.

A mushroom trip this summer opened my ears to Alice Coltrane. I walked out into a garden as this song was playing randomly from a playlist https://www.youtube.com/watch?v=Hn36bzFZeg4&ab_channel=Alice... (Coltrane at her more serene).

I had a magical moment where I was listening to her music and looking up at the sky through the tree crowns. After that I've been listening to her regularly.

We're all activists.

I agree with you from a technical standpoint — something created for displaying and navigating between documents is being misused for distributing apps.

At the same time though none other model affords the same distribution, write once run everywhere. No other distribution platform can compete. And users have become accustomed to the web being apps as well as documents. In fact, many have become accustomed to more or less treating their web browser as an OS (or more realistically, not giving the distinction any thought).

Maybe an interesting way forward could be a web model specifically for apps, which of course many would say would be WebAssembly. The HTML/CSS/JS combo has been remarkably successful and resilient though, so I'm not convinced it will be dethroned easily.

Lab-Grown Meat. Potentially revolutionary impact on reduction of animal suffering and climate change.

Agree, does seems high.

For sure. Conflicts of interest are too common in nutrition research, and I think the criticism of this particular paper is laudable.

I simply wanted to point out that there is significant indications from other studies that red meat, and in particular processed red meat, is correlated with heart disease (and cancer).

It's far from one study that has found a link between red meat and heart disease.

https://pubmed.ncbi.nlm.nih.gov/?term=meat+heart+disease

Faulkner: The Sound and the Fury

I've used Tailwind on many projects at work for about a year now. I do not like it.

Tailwind seemingly affords an easy way of writing inline styles, but it 1) clutters the HTML, 2) leads to repetition and makes people break the DRY principle (yes, you should extract to components, but people don't always do that), 3) uses names that can be similar but are not identical to CSS properties and feels like a bad abstraction.

If you use something like Svelte, where you can write local CSS within a component I fail the see the benefit of Tailwind. For me Tailwind is the most ill-conceived frontend tech I've had to use in later years.

> Python has problems scaling to medium-size code bases because programs above a certain size tend to become difficult to reason about.

In mye experience Python programs are not more difficult to reason about than equivalent Java programs. To the contrary an over-reliance on certain design patterns and ubiquitous, inescapable OOP complicates Java code bases, while the static typing is so weak it affords little safety compared to e.g. Python.

Worth keeping in mind a that a Python program will be about half the LOC of a Java program doing the same thing. (See the reference section here [1].) In other words you can get further with Python before passing the complexity threshold.

Bugs are also proportional to lines of code [2], which is another element that favours Python over more verbose languages like Java.

1. https://svese.dev/comparing-java-and-python-is-java-10x-more...

2. https://amartester.blogspot.com/2007/04/bugs-per-lines-of-co...

Cool, that makes it more interesting for me. (By the way, the video on that page (https://thin.dev/docs/svelte) still uses React, though the text does descripbe a setup with Svelte.)

Are there any plans to decouple this from React, either by making it framework-agnostic, or by adding support for other frameworks like e.g. Svelte and Vue?

Not for me. Bootstrap is very mature, has sane UX, is adaptable, has a good balance between general styles and utility classes. I find that Tailwind clutters your HTML and I fail to see the benefit over writing pure CSS in isolated components in a framework like e.g. Svelte. The reason I would use a CSS framework in the first place is to avoid having to write everything from scratch myself. All (the free parts of) Tailwind affords is an indirect way of writing styles using classes. In that case you might as well bite the bullet and learn CSS properly.

I think Rails is the best fit for this, alternatively something like SvelteKit + Supabase (the latter if you need a db).

For me it seems React has made some unfortunate choices in an attempt to go FP in a language that does not afford it very well. Instead of embracing JS and working in alignment with its limitations/offerings, the React team has introduced elaborate workarounds that gives a whiff of FP but introduces indirection and verbosity and does not solve basic problems of state (i.e. the example from the blog post with classes vs. closures).

I prefer frameworks like e.g. Svelte that works with what JS affords. If you want to go full FP Elm or ClojureScript will give you more value for your money than React imo.

Both, likely.

If consciousness is not embodied that would imply metaphysics and body/mind dualism, e.i. something countrary what one might term the scientific world view.

SvelteKit + Supabase or Rails.

This is unfortunate indeed. I'm hoping the Kotlin language server for VS Code will get some love, it doesn't seem to be working at this point.

> After that you have to choose a framework, because Java applications are very framework-heavy ones. And that's where most of complexity comes from. People usually use Spring these days, so that's probably would be the most reasonable choice. There's no easy path, you'll struggle a lot and that's unavoidable. Modern Java Frameworks are full of hard to grasp concepts, tricky magic code and 20-year old roots buried in the depths of stacktraces.

Honestly that does not sound like a culture/ecosystem it is pleasurable to work within. Why wouldn't people choose something more modern and lightweight than Spring?

Indeed Tegnell sacrificed the old and the weak in line with the old Scandinan tradition. https://en.wikipedia.org/wiki/%C3%84ttestupa

Compared to Norway the number of covid deaths so far is about tenfold higher. How that counts as success is beyond me.

https://ourworldindata.org/explorers/coronavirus-data-explor...

The author doesn't say who or how what about the project was interesting, just that it was interesting and that it made him endure Java. My experience is the opposite. I don't care so much what I'm making, as long as it's not something making the world a worse place. I care about what technology and methods I can use to do whatever. That is interesting to me from a craft point of view.

Delta-infected patients seem to be 1.8 times more likely to be hospitalised, compared to Alpha-infected patients [1]. Since the covid virus takes two weeks plus to kill its host and also spreads while the host is asymptomatic, there really isn't much selective pressure to make it less deadly. So far infectiousness and severity of disease has gone hand in hand with this virus.

1. https://www.bloomberg.com/news/articles/2021-07-23/what-make...

I'm surprised Kanban is only mentioned cursorily. Limiting work in progress is one of, if not the, point of Kanban.