ItsYan

I live in an apartment as well and my area has really good transportation. We don't commute to work with the car. There are various reasons why we did car-sharing nonetheless.

In the end our family decided to buy a car. We got an EV. Our use is sporadic and one could argue that if money was our priority, buying the car was a mistake.

So in this situation, having an EV is fine. The only downside that I found is that I spend a bit too much money on McDonald's. This is because the cheapest chargers are next McDonald's where I live. But it's not a problem, just a funny hiccup.

I understand your viewpoint because but also have you considered that your approach adds nothing to the builder?

I don't mean this in a judgemental way. In your scenario, I spend learning 50 different technologies that I will never use because they are not hired for. Whereas the colleague makes 50 different projects, gets comfortable with the technology and maybe hits an interesting edge case or two to talk about at their next interview, if they are lucky.

I am saying this as someone, who has tried to think about complexity and what not in my projects. But it turns out that I get a lot more mileage from practicing deployment with k3s than know what Dokku and Kamal do and how to deploy the app directly as a process.

I wonder if this is true in continental Europe.

As an EU citizen, I can't tell you if it's true for the immigration office.

But for anything else? Kind of? If you want to move, you have to make an appointment in person to tell them. But it is also retroactive, so you can move and then make an appointment in 5 months and it's fine. The paper that says where you live is very important but it's also easy to get, you just have to show up. Not any time but the times for that are plentiful enough that it works out.

What makes my blood boil is the paperwork for when your kid is born. It feels like they should just be able to retrieve everything from their database but you have to submit a load of documents anyway and it has to be original.

Also, don't try to get married in Germany. Just go to Denmark, much easier, despite the delays if you get something wrong. You can do the whole thing in English and you don't have to translate anything for Germans after, if I recall correctly.

If you don't have to deal with the immigration office, it's fine. If you do, then good luck. I heard it's a pain. For example, in Bremen, it takes at least 2 years to process a citizenship application. It should take a year at most. So I guess if you ever wanted to sue someone and win a slam dunk case, you could do that in Bremen. In Berlin, the citizenship application takes only a few months.

Vote and join a party

I don't believe this. The sundvik series feels way more complex than brimnes but wardrobes have the same complexity score.

On the other hand, the Brits will happily switch from their accent/dialect to accommodate a foreigner.

No such thing has happened to me in Germany.

Tja, Nie im Leben würde ich zu Bayern gehen.

I'm surprised that despite its claim to openness and tolerance, cities like Hamburg, Bremen or Hannover are not capitalising on this.

>It is not so much that, but rather that if you hire average people with average skills or people that require training you go out of business because the shop next door won't.

If only workers would form some kind of a community, which would take monthly contributions and that would then be used to upskill. It would unite most, if not all people in the same industry.

I feel like this advice is not very useful because when you call yourself a software engineer or programmer, you are doing it in order to sell a service.

Your customers are companies looking for someone to slot into a box called "software engineer" and so you sell yourself as such. Nothing wrong with that.

We should also note who Patrick was at the time. He was an SEO consultant and in general a business development expert. It just also happened that he was able to code. And he was very very early to the field. An SEO expert was barely a thing.

So if your only skill is software development, then of course you would call yourself that. And if your main skill is SEO or some other marketing channel, then you call yourself that.

I think the real takeaway from the advice "don't call yourself a programmer" is to search the market for higher paid opportunities, where you can still leverage coding. And you can call yourself a programmer while doing so.

I installed eOS on our car phone the other day so that my wife can try it out, with Fairphone in mind.

Neither one of us has used it much so far but it's uncanny how iPhone like it feels. Though I've never owned an iOS device.

It's day light, not sun light. You can easily burn on a cloudy day.

People can choose to use online services to game or other various ones for compute. The demand is surely more elastic than food and fuel after a natural disaster. The consumer can also forego any purchases.

Let's say what happens in a decade or to. All injustices have a weird way of hitting back decades after.

People want this but I don't think it actually delivers, even if it did exactly what it promised. The issue there isn't with the tool, the issue is that the engineer doesn't want to cooperate.

The engineer will either output garbage or output nothing at all. So you will still need a human to pester the dev.

People like to hate on BMW drivers but a BMW driver was the only person in a hardware store parking lot to help me with jump-starting my car.

I am going through interviews with founders on https://www.startupsfortherestofus.com/ and it is indeed what happens.

It is not straightforward, however. One guy did only product-led marketing and it took him 3 years for his SaaS to make good numbers. And he's probably an outlier, since he's featured on the show.

And then you have another guy, who blogged for 5 years about Ruby and only after those 5 years using the audience from that, he built an OSS project with monetisation on top of that. But he could do that because he talked to his audience about ideas.

Listening to those interviews, I get the impression that if you know what you're doing, you can make a profitable SaaS in 2 or 3 years. But to get to a state, where you know what you're doing, you need at least another 3 years or more of actually putting in the reps in an honest way.

And I think that's where the "increase your luck" comes in. I think it's kind of shallow non-sense in the vein of motivational speaking but lots of people like this kind of content and like to be aspirational. Lots of the books sold by internet hustlers, like Rob Walling or Aaron Francis, don't get read, only bought.