dosethree

it can assist with preventing transmission https://www.mdpi.com/2673-8112/3/10/103

you shun unnecessary complexity.

If you dont think that exists in java, spend some time in the maven documentation or spring documentation https://docs.spring.io/spring-framework/reference/index.html https://maven.apache.org/guides/getting-started/ Then imagine yourself a beginner to programming trying to make sense of that documentation

you try keep the easy things easy + simple, and try to make the hard things easier and simpler, if possible. Simple aint easy

I dont hate java (anymore), it has plenty of utility, (like say...jira). But when I'm writing golang I pretty much never think "oh I wish this I was writing java right now." no thanks

Bitbucket is butt

Just use tmux and split windows

I've never heard of german cars being known for most reliable. And when they break they are the most expensive to fix. For example audis always had issues with oil leaking and in the US audi mechanics charge the most per hour and they are hard to work on.

according to consumer reports, bmw is the most reliable at 9th most reliable automaker, audi and merc are way down

Yeah but what are the politics of the people who profit from traditional car makers?

How many users do they have though?

fantastic article

just abolish the patent system entirely. at minimum, for software

Yeah I actually looked up whether preventive is cheaper, and while it may be in some cases not in all. It does sound overall BETTER though because it will result in better health outcomes. but the aging population is obviously a massive drain on medical costs and theres not much we can do

If I lose my job I lose health care. How does that make any sense? Preventative medicine is cheaper

This website looks like they copied glassdoor's looks right down to the CCS. Looks like a fake website

It had basic geolocation feature though so you could mostly see where you were on a map which was still very useful compared to flip phones

A lot of buildings down have floors under floor #1 so its always above you

Companies just want a clean break. In cases where they really need you to do a hand off, you will get a transition period. I've had that happen to me, and it's a weird feeling. I don't think its great for productivity or morale, and is more common when you are shutting an entire division down.

The difference is sort of meaningless. What matters is if you are getting severance or unemployment, and if you can get a recommendation. If they are going to fire you for invidual performance, youd think they would put you on a pip, but some companies will just wait and lay you off.

But the two can be similar in that if you are valuable you won't get fired or laid off, unless the company is in serious trouble.

Sometimes you are just on the wrong project. It is good to be generally aware of your projects value if you want to keep your job.

Cucumber, IMO, died like 8+ years ago and never really made sense. It was useful for a team to define requirements and then see the progress to implementing them, but Gherkin was a sticking point and integration tests are hard to get/keep working, esp with javascript apps that are now so popular. The fact that someone would pay a OSS maintainer up til now seems like a crazy waste of money.

yep. An awkward terrible joke to cover up whatever she was doing - social media, messaging, or looking up her employer

Sounds similar to how do not call lists are handled

This is super common, (and the mark of a bad programmer if you program the same in every language). What's funny is the opposite - people who get so into ruby that everything they write is cute and overthought - is actually worse.

Ruby is so powerful but simplicity is the best if other people are going to read and maintain your code. Go is great for this.

golang https://github.com/Masterminds/squirrel

Constructing sql by concat strings has a few issues, its repetitive and hard to assemble certain queries conditionally, and at least in golang its easy to write code vulnerable to sql injection and you can avoid that by using types

Bitbucket wikis basically do this.

Expensive wines are expensive because they are rare, not because they are better. If you value your money its not for you. The same is not true of beer, I can't really say with liquor

If you are searching for jobs or something, "go" is not sufficient

Maybe its just my team, but dev's dont need to know k8s. It certainly doesn't hurt, but they should be able to write code and get their jobs done without knowing much about k8s at all. Basic shit like how to get logs, but thats a given for all platforms

Ultima online was the coolest. Heres one of my stories. In UO housing was at a premium. Buying a house was a big deal. But if you didnt periodically log in to refresh your house, eventually, it would start to crumble..

Since you could tell which houses were about to crumble, and crumbling means all the belongings in the house would fall to the ground and a new house could be put in its place, this was a big deal. Campers would come from all around to camp out all the falling down house. Guilds would show up. Anyways during one epic battle at a house near the coast, my buddies and I were camping out at the house to try to get some loot. Battles ensue At one point, a bunch of role players pulled up in a boat from the coast and started shooting arrows at everyone trying to camp at the house

Factors for me are: 1. how hard will it be to remove/replace this package in the future? how much coupling does it introduce? 2. how likely will it be that this is deprecated/unmaintained in the future

For sure, I had all this stuff before k8s as well

K8s ate everyone else. The alternative is to use a heroku like sass

You don't even end up spending time on Kubernetes, because k8s is just part of the solution, a container scheduler. You have to bring logs, monitoring, a container registry ,as well as a CI system with custom jobs and do integration of everything.

IMO people who describe themselves as big fish in a small pond come off as extremely arrogant