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)

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

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.

I don’t think it’s because you grew up poor. It’s because why would you buy coffee everyday?

I buy coffee almost everytime I’m at an airport or a train station, but that’s like… once every two months? If I would commute by train, I wouldn’t buy coffee everytime I’m at the train station, I would just wait until I’m in the office to grab a cup.

But I did buy a coffee daily, when I was in university. There was no way to get a coffee besides buying one, so I bought one. So I think thats the main thing about buying daily, necessity. Some companies only have paid machines, so you buy a coffee daily when at work. In school or university you don’t have a coffee machine available, so you buy one daily.

I don’t want to set a misunderstanding: this does not solve the state on reboot issue, maybe “flawlessly” is not the correct word. On a reboot, all automations are always stopped, so that does not help here.

It’s also important to set the mode of the automation to “restart”, then it works flawlessly

PgUp and PgDn are also extremely useful when scrolling through logs

Technically: Thats no app but normal messaging

The number behind is not the real phone number from the boss, but a forwarding number. If you send a message to the number, the message gets in a queue for the boss to read and he will see the message when he is back in office.

Actually: While these kinds of services exist, they would result in a green message box in iMessage. So here it’s clearly just a joke between pals

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

I don’t really code in my free time, every merge request for a FOSS project I wanted to do so far was for company projects where a feature was missing or buggy. My GitHub and Gitlab accounts are full of outdated forks we needed for a minor change in the FOSS project which I was not allowed to merge upstream

FOSS user:

Wants to improve the software and sees easy fixes, but isn’t allowed to create a Merge Request because company policy disallows you from writing code for other projects on company time

Shared hosting sounds like you don’t have your data stored privately and doesn’t sound like less work for the company.

Don’t look at the name from a technicians perspective, but from the perspective of a manager of a small startup who wants to reduce the overhead for hosting it’s service as much as possible. Also serverless is not wrong per sé, it’s exactly what you as the customer get.

You could spin it the same way for every other instance. Why do you call GoDaddy “shared hosting”, in the end it’s just a pod on a kubernetes cluster. So why don’t you call it “private kubernetes pod”?

I think that’s the main reason, it’s a good name explaining what you can expect: an environment where you don’t have to worry about servers and don’t need an administrator

There are eggs and a bottle of water

Nope. It’s a nightmare. The ad company now knows that you are friends or family