I just googled “BASF T-Shirt” and immediately found the one he is wearing in this video (and he wear it in a couple of other videos recently)
I just googled “BASF T-Shirt” and immediately found the one he is wearing in this video (and he wear it in a couple of other videos recently)
Just using fluentd to push the files into an ElasticSearch DB and using Kibana as frontend is one day of work for a kubernetes admin and it works good enough (and way better than grepping logfiles from every of the 3000 pods running in a big cluster)
And if something breaks they put the burden on you for not creating backups. Always keep it in writing that you are supposed to work on something else, otherwise you will get the problem down the line
Yeah, I bought it for 10ct
yeah thats why I said it only has the chance, not that it leads to good code
The only thing that has the chance to prevent unmaintainable garbage code is a plethora of linting rules.
I don’t see people hating discord for it, just pointing out that it was a bad choice from the beginning
The adapter is still the inconvenience for me, just because the other option is a (tiny) inconvenience for you doesn’t change the fact that the adapter is an inconvenience for me.
The adapter IS the inconvenience.
All of scandinavia. There are public registers where you can look up the salary of everyone for norway, sweden and finland. When these registers were introduced, the salaries were normalized across the whole population
PgUp and PgDn are also extremely useful when scrolling through logs
This has nothing directly to do with The Day Before, but: Backing a Kickstarter is something completely different and that has to come into peoples heads. Preorders are for a mostly finished product that will 100% ship. The devs have enough funding from investors and publishers, the game will be released no matter how little preorders they will get. Crowdfunding however is for an idea in its infancy that might never be finished. Crowdfunding is an investment.
But where is the difference in this case, The Day Before? Well, easy: When you invest in a kickstarter, the company has to use the money you invested to actually develop the game. They can’t buy fancy cars with the money, they need to put it to good use. If the company uses the money for their own personal benefit, they can be sued for that. For preorders thats not the case.
I couldn’t disagree more with you.
It’s pretty obvious that they only published the game in the current state because of the lawsuit. The game is a total scam and they deserve the hate from the people that invested a lot of money when backing. Backing on Kickstarter has something to do with trust. Of course, the project may never be finished and that’s okay. But it’s obvious here, that they just took the money and did not use it for the game.
From one Datacenter? Yes. If you put all datacenters into the sea? Definitely not. And if the Bitcoin scumbags decide that this is a good idea and built huge mining farms underwarer it’s even worse. Datacenters are one of the biggest contributors to energy need already, taking up 1-1.3% of global energy demand. That’s no joke
I don’t think that this would work, there are no types anymore during runtime because everything is translated into plain js on build. TypeScript only exists during development
The main problem with JavaScript and TypeScript is that there is such a little entrybarrier to it, that way too many people use it without understanding it. The amount of times that we had major issues in production because someone doesn’t understand TypeScript is not countable anymore and our project went live only 4 months ago.
For example, when you use nest.js and want to use a boolean value as a query parameter.
As an example:
@Get('valueOfMyBoolean')
@ApiQuery(
{
name: 'myBoolean',
type: boolean,
}
)
myBooleanFunction(
@Query('myBoolean') myBoolean: boolean
){
if(myBoolean){
return 'myBoolean is true';
}
return 'myBoolean is false';
}
You see this code. You don’t see anything wrong with it. The architect looks at it in code review and doesn’t see anything wrong with it. But then you do a GET https://something.com/valueOfMyBoolean?myBoolean=false
and you get “myBoolean is true” and if you do typeOf(myBoolean) you will see that, despite you declaring it twice, myBoolean is not a boolean but a string. But when running the unit-tests, myBoolean is a boolean.
I hate Typescript for promising me that nobody can put cyanide on the list, but in reality it disallows ME from putting cyanide on the list, but everyone else from the outside is still allowed to do so by using the API which is plain JavaScript again
Why would they keep it on? Sure, they will continue to collect data for their AI, but I’m pretty sure they are happy that they don’t want to keep it on if it might drive you to use other search engines. And turn it back on after a few versions of optimization
Was the same for me this vacation. Gladly we were on a smaller mountain which was completely surrounded by villages, so we knew that just going down the mountain would lead to a bus that could bring us to the hotel, so we didnt care that much.
no it’s the joke. In o-notation you always use the highest approximation, so o(n!²) does not exist, it’s only o(n!)
Otherwise there would never be o(1) or o(n), because o(1) would imply that the algorithm only has a single line of instructions, same for o(n)