furstenheim

I once asked hr from a position advertising "unlimited PTO" what was the average of PTO days in the team. She panicked a little bit

I haven't used sqlfluff, but they support jinja templating and in those cases they ignore spacing problems. So maybe your use case can be supported?

Effective Java by Joshua Bloch is really good. Some of the learnings only apply to Java, but most apply to any language.

All the tips are very focused on how the code, APIs and even the languages evolve, trying to understand how your changes could confuse other developers. Compared to clean code, it's clear that it's written by someone who has done a lot of coding and seen the evolution, with a very pragmatic approach. Not just theoretical like Clean Code

When dealing with go errors I like to give them proper names. barErr, fooErr. In the case of the article it fixes reordering (not that you do that a lot in real code). In real code it makes unhandled errors a compile error, because the variable is not used.

> There's an evolutionary reason why plants do not naturally grow this big.

That could be said of current crops. They are the result of years of artificial selection

The main problem with in memory databases is that they are not the same database. I've had several issues which I had to find a fix that worked on one database and was legal syntax on the other. Say maybe one database allows force index but in memory does not.

I've even seen one database layer for in memory and a completely different one for real database. That means that your unit tests are not really testing your production code

Not as extreme as PlsExplain. But in JavaScript you can also describe what you log using babel https://github.com/furstenheim/babel-plugin-meaningful-logs

The article is way more nuanced than the title.

That said, if the virus spreaded the same with the vaccine, the advantaged would be that the virus wouldn't have as much evolutionary pressure to change and become resistant. For example, it could make it harder for lambda variant, which might be symptomatic, to become prevalent

This looks a lot like evolution in real time.

Until you have an emergency and you need to call the helicopter, been there

Related to the topic https://threatpost.com/100k-google-cloud-shell-root-compromi...

Data centers execute code and that could be hacked

For postgres if you self host then you can create ad hoc native extension. Most of the time it's not needed, but I've seen 2-4x speed ups in critical queries

Yes, it's a pity that java applets have disappeared. Great UX, great development cycle, programming purity... </s>

Eslint is the default linter. Standard is a curated list of rules with good quality.

https://github.com/standard/eslint-config-standard

I would start with that and tweak what you don't like

It looks interesting, but how does it behave with dynamically created queries?

Not really, Electron would be the tool but not the end goal. Here an ORM is the end goal and that's what the parent complains about.

This is kind of what happens with Postgres. Postgres in itself is great and simple to use. However, managing replication, maintenance, sharding... Is often quoted as very complex in the conference themselves. And that's precisely what most of the companies around Postgres live on

Something that work for me, have a websocket open to the client and notify him that it's done. Additionally register this notifications in the database, so that if the user had closed the browser he'll see the notification next time that he logs in

I've always thought something similar should apply to stackoverflow. Points from newer questions should be worth increasingly more, as more and more questions (specially the easy ones) are already answered

We got a huge company using IE11, they could not update to Chrome because "it was not secure" according to their IT department

Specially since it can only done in Eclipse xd

This article is not very good in convincing that prototype pollution is a problem.

There was a write up about the kibana rce that really shows it's a problem:

https://research.securitum.com/prototype-pollution-rce-kiban...

I don't mean lombok as a library, which works. I mean developing lombok itself

100% lombok can only be developed on eclipse. They have an open issue to make it compile on intellij...

I'm surprised it didn't mention the more extreme case of Mike Merrill https://www.wired.com/2013/03/ipo-man/

This looks really useful.

Paradoxically, I find that the terminal is the place where I end up using the mouse the most.

Lots of red flags there:

- Dev installation guides with credentials to prod.

- Tests that delete everything, not just what they create.

- The obvious of giving access to delete production on the first day.

- Where they lacking backups?

I find value in part of it. Dailies I find very beneficial. You get to hear what other people are having problems with, and maybe you already faced something similar. Or the other way around, when you face it you remember that someone solved a similar issue.

Totally, and if you mix it with yarns plug and play you should get best of both worlds

Yeah, maybe "deal breaker" is to strong. But I've had consumers of a library not being able to use it because a critical dependency (html parser) was not the same version as they had