Du wirst es nicht mögen, aber echte Männer essen eine undefinierte Masse, hergestellt aus den künstlich gestreckten Überresten von mit Hormonen und Antibiotika vollgestopften Tieren, die ihr Leben auf 0,6m² verbracht haben ohne jemals die Sonne zu sehen.
Die gute alte Claire Grube, da fehlt dann aber noch ihr Lebensgefährte Rainer Zufall.
While vegetarians won’t eat things that caused harm to produce
This is nonsense, since there is a lot of animal harm involved in the production of eggs and milk.
And I don’t see the contradiction you are seeing. Your piracy argument is pro music/movie industry and the vegan argument is against the meat industry. Doesn’t make much sense to equate those arguments.
Ich finde schon, dass man da unterscheiden sollte. Arona und T-Cross sind näher an meinem Polo von 2014 als an den richtig großen SUVs. Ansonsten hast du aber Recht.
Hab mittlerweile zwei Kinder und bin auf der Suche nach nem neuen und etwas größeren Auto. Es soll auf jeden Fall elektrisch sein, aber da ist die Auswahl irgendwie enttäuschend. Ich saß heute mal probeweise in nem Opel Mokka, der ist zwar außen in alle Richtungen größer als mein Polo, aber innen merkt man davon quasi nichts. Immerhin gibt es mittlerweile ein paar Kombis.
Ist halt echt so. Z.B. T-cross und Ford Explorer zählen beide als SUV in die Statistik, letzterer ist aber ein ganz anderer Brocken
https://www.carsized.com/en/cars/compare/volkswagen-t-cross-2019-suv-vs-ford-explorer-2019-suv/
Gibt sicher noch extremere Beispiele, aber das waren die ersten die mir einfielen.
I was using Mozilla in order to not use Internet Explorer and at some point I switched to their new browser when it was still called Firebird.
Nowadays I stick to it just so Google doesn’t get a browser monopoly.
It’s a random list for sure, but vendor lock-in can also be a problem for companies hosting their stuff in the cloud in a similar manner to what’s happening with unity.
A simple website to show if it matters to you is this one (ideally check it on a screen with more than 60hz):
Everyone’s perception is different, I’ve met someone who couldn’t tell the UFOs apart past 30 fps. They also didn’t like shooters/action games much, probably because following fast movements was difficult for them.
But I think the vast majority of people easily notice the difference between 30 and 60. And 60 to 120 should also be possible notice for most. As for me, I used to play Quake 3 a lot and back then that was played on 120 or even 240hz CRTs. The first flat screens with slow reaction times and 60hz max were quite a step down.
While I don’t really like linus tech tips, they did some nice testing on the topic and came to the conclusion that more fps is measurably better for shooters, even if the refresh rate can’t keep up.
I’ve been on-call in 3 of my past jobs in Germany, most of it was pretty similar, 1 week per person, 600-800€ per week and some extra pay on incidents. Current job:
I thought it was a non-issue that tooling should take care of anyway until stackoverflow published this:
https://stackoverflow.blog/2017/06/15/developers-use-spaces-make-money-use-tabs/
Spaces all the way
Good questions, I could probably write a lot, but I’ll try to keep it short. I usually apply TDD and there are different schools of thought within it about how to structure the development process. But no matter how exactly you do it, if you focus on writing the tests while writing your code, you won’t end up with an application that you then have to figure out how to test.
what to test
Well, what is the application supposed do? That is what you test, the behaviour of the application.
So in a codebase without any tests, the first thing you should write a test for is the happy path. That will probably not be a unit test. So for the web server example, set it up in a test with a file, start it and check if it serves that file.
Then you can add tests for all the error cases and for additional functionality. You can write unit tests for individual components. The ideal places to test are interfaces with clear boundaries. Ideally you should not have to look at the code of a method to be able to write a test for it. In reality that’s not always so easy, especially in existing code bases, but if you have to set up more than one mock, it tends to lead to brittle tests.
Every time you encounter a bug/issue, reproduce it in a test first. And do measure code coverage, but don’t make it a target, just check for places that are lacking.
Here you go: https://codegolf.stackexchange.com/
But on a more serious note, I don’t really agree. Writing more code needs to be a conscious choice, but going for the shortest code too often creates a mess. I know, since I was that junior dev who just wanted to get stuff done and I would ignore project architecture in order to have to implement less, like accessing the database in GUI code.
Shorter code with the same amount of coupling between components and with the same readability is always better though.
But does it have to be? I haven’t touched non-web GUIs since 15 years, so my perspective on this is limited. And web frontend is not what I would call a well designed system for it’s current purpose.
Nice, so they are hot takes :D
If the design of a code change is bad, noticing that in the PR stage is not desirable. It should be discussed before someone actually went ahead and implemented it. It can also happen if people misunderstand the architecture, but again, that should be cleared up before actually implementing a change. Code style should be enforced automatically, as should test coverage and performance. Code review is also pretty bad at finding bugs from my experience. That imo leaves very few things where code review is useful that are not nitpicking.
As for programming languages, the amount does matter for individuals and for teams/organisations. A developer who can only use a single language is not very good, and using a many different languages within the same team is not good either.
Even better is to ship small increments often.
Unfortunately in many organisations, leadership doesn’t really understand that instead of reducing quality, scope should be reduced in order to ship faster. And developers rarely have a say in these things.
While I agree that it can be considered a hot take industry wide, I don’t think for most devs that is a hot take, the ones whom I’ve seen ship broken stuff were rushed on tight deadlines and didn’t have the experience/motivation/political capital to fight back on deadlines.
Not sure if these are hot takes:
A small loan of a million dollars