skysight-inc/HackerNews huggingface dataset:
The core k8s, not that bad, once you've learned where to look - logs on pods, events, and kubelet logs from journalctl. That last one is important not to forget when debugging plugin controllers.
I'm less than 15 years from retirement age, and I don't expect to get any Social Security.
More importantly, you're not in a hierarchical power relationship (probably) with your spouse. And at some point after management has demanded some amount of initiative and workers have implemented some amount of things on their own initiative (which is another barrier), there's a big question of why there's a manager at all, or at least why they get paid more.
One spouse does the super commute and the other works closer to home/school or maybe not at all. Otherwise you're having to hire sitters, caretakers, etc.
Given GKE or AKS, not quite sure how "shell scripts, the AWS API, and cron" is "much simpler" than:

$ docker build . -tag gcr.io/google-samples/hello-app:1.0
$ docker push gcr.io/google-samples/hello-app:1.0
$ kubectl run hello-server --image gcr.io/google-samples/hello-app:1.0 --port 8080
$ kubectl expose deployment hello-server --type "LoadBalancer"

where the Dockerfile content is:

FROM golang:1.8-alpine
ADD . /go/src/hello-app
RUN go install hello-app

FROM alpine:latest
COPY --from=0 /go/bin/hello-app .
ENV PORT 8080
CMD ["./hello-app"]

https://cloud.google.com/kubernetes-engine/docs/quickstart

https://github.com/GoogleCloudPlatform/kubernetes-engine-sam...
Stellar: Price Analysis, June 06
The project is private.
I use it for server-rendering React in a Spring app
> intentionally designed to waste electricity.

I strongly doubt the intention was to waste electricity, more likely it was incidentally designed that way, as it's difficult to conceive how you could create such a decentralized cryptocurrency without proof-of-work (at least at the time).
Correction: seemed
Geoffrey's Loophole
One interesting side effect of this will be on the interest rate.

Social Security has been investing the surplus, most (or all?) in Treasury bonds. As outflows exceed income, they're going to have to sell bonds. That should drive prices down, and therefore interest rates up - to what degree, I don't know.
App service is alright but I'd recommend Heroku over app service any day. However, there is some visible work being done to improve app service like supporting docker compose files to run multiple containers but the basics are still very painful.

Most notably, swapping servers (slots) always caused downtime, accessing logs was flaky and slow, azure interface is just plain slow, continuous deploy was flaky (or it just didn't kick in until 20 min later?) and I had to manually restart servers many times
My experience is just the opposite in my 22 years. I've only twice received a raise of more than 3% - once in 1997 when I was "promoted" to a junior programmer from a computer operator ($11K) and once again in 2000 at a different job with a ($10K) market adjustment.

I learned my lesson after 7 years of COLAs (I was a slow learner /s). Jump ship at the first sign that the company won't pay you your market rate.

Now 10 years, 5 jobs, and $70K later, I don't expect major jumps anymore. I'm within $15,000 of the most that any company in my local market is willing to pay an individual contributor. I have no desire for management and I live a comfortable life.
Rolling back on dev only is still bad. That is developing and testing against a version of the database that you know will never be prodlike. The dev database should be created by snapshots or forward migrations from scratch.
Your first sentence doesn't make any sense. If it's one party, eg Russia or China, then these aren't two unknown parties working together, they're one party operating at two locations. Russia and China both have the reach to operate in Cuba and China, both are devoted adversaries of the US when it comes to politics, espionage and military.

Further, it may be espionage gear that both Russia and China are now using, such that one party (Russia) is using it in Cuba, and the other party (China) is using it in China.

That is all a lot more plausible than the US severely harming their own people at their living quarters in multiple locations around the globe.
The database really is an API, in that client code depends on it and its structure will be difficult to change once you go live, whether you want that to be true or not. Writing the API before code that depends on it seems like an inherently good idea to me.

You can pretend like you don't need to figure these things out first and get away with it for a while, but at some point the lack of a solid foundation is going to bite you.

I think all devs should answer the question, "What if they don't want to use my UI or interface, or they want to automate something?" That's a good scenario to support for any client, including yourself.
I take it that’s a no for you.

I’ve only ever had one union job (at a young age) and that told me everything I need to know about unions.

Ultimately if you’re not getting paid what you’re worth, that’s on you. Or you’re wrong about what you’re worth.

I guess our difference is that I’d rather myself to blame for poor negotiating than some union boss, making twice what I make, telling me what I’ll be getting with no ability to negotiate.
> Even accounting for inflation and investment, the average worker still is paid out more from Social Security than they paid in.

The source cited combines “Social Security and Medicare”, it doesn't (at least in the quoted excerpt) address SS separately. These are different programs supported by different Trust Funds funded by different taxes applicable to different income and with different dynamics driving costs.
We don't have that distinction in English, either. Words derived from names just tend to lose their capitalization over time and may gradually be diluted in meaning as people use them without understanding their origin.
Necessity is the mother of invention.
Oh sure. It was more a point about software polish. All these SoC's have hardware support for clock gating and separable power domains and deep idle states, etc...

But in general, making all junk work is a huge rats' nest of complexity. And in practice, except for a tiny handful of devices from top-tier manufacturers, it just doesn't. Maybe it works "most" of the time. Maybe there are tuning tricks you can use that get the power down but break two or three devices in crazy ways.

But Apple has the smarts and resources to ship a power-hungry part and guarantee that it sits at a clean idle reliably. And Qualcomm isn't far behind as long as they have an integrator like Google or Samsung breathing down their neck. But all the other junk? Yeah, junk.
Asynchronous communication is like eventual consistency.

It seems pragmatic until you actually struggle to get everyone to be on the same page at the same time, then you spend a lot of time figuring out how to be consistent.

I agree the video calls are probably over the top - but asynchronous communication != synchronous communication.
Wrong in most aspects. Right to work effectively ends most labor monopolies that unions have erected. By removing the monopolies, workers have far better choices about whom to work for, and how to negotiate wages.

Here's a simple example of the power of monopoly and oligarchy. The recent wage fixing kerfuffle over at google, apple, FB, and others resulting initially in depressed wages for workers. Upon breaking up that oligarchy, and putting those companies on notice ... what has happened to wages?

If I believe the pro-union folks here, then they have fallen dramatically, and workers are at a disadvantage in negotiations.

However, I believe in market economics, the invisible hand of the market, and see it in action here. Wages have risen dramatically, as the market distortion due to the oligarchy has been removed, and labor is free to discover its price.

Had there been a union ... this would not have happened. You would have a floor and a ceiling. More productive workers would not seek to increase their wages by working harder, or switching companies. Demand would be distorted.

If you want to be able to negotiate wages, you need leverage. Leverage in the form of a union is well understood, and has consequences for locales. Leverage in the form of demand (get multiple job offers, create a market making enterprise for selling your labor, select the highest/best offer).
> Why should both exist?

In general, I dislike existential questions about programming languages. No one seems to do that for other product categories. "Why should Monet and Renoir both exist?" "We already have Castlevania. Why do we need Metroid?"

I understand languages are a little different because each requires an ecosystem that is fueled by programmer attention. There is an opportunity cost that time developer X spends writing a library for language Y is time not spent writing a library for language Z.

But, overall, I try not to get too hung up on that. I find thinking of things in zero-sum terms stressful and often not very useful. There are enough programmers to support a wide variety of languages. If we're worried about not having enough total nerd capital to support all of those ecosystems, I think there are plenty of other inefficiencies we could focus one. Eliminating the 7,000+ different Node libraries for doing asynchrony would probably free up a few person-decades of effort.
Show HN: Inject AWS SSM Parameters as EnvVars in your Docker images
The most concerning aspect of this is the lack of details surrounding the initial attack vector and the fact that the IoC list is effectively useless to anyone downstream of these devices which sit at the perimeter of your network.

Anyone else having fun with the minor panic attacks incited by slow page-loads?
The fundamental/fucked-up thing is that if you cut the military budget it's not that soldiers stop getting recruited it's that tank/jet/boot/GPS/mre companies start firing people. The Military Industrial complex is a huge welfare/workfare program that no one in power is willing to cut. So until we can convince essentially EVERY voter (any party: libertarian, green, D or R) that it's okay to have a real safety net then politicians who campaign against the military budget are basically lost causes.
What does the JVM language specification say about this? That's a pretty universal opinion we can all agree to follow.

15.7, Evaluation Order:

> It is recommended that code not rely crucially on this specification. Code is usually clearer when each expression contains at most one side effect, as its outermost operation, and when code does not depend on exactly which exception arises as a consequence of the left-to-right evaluation of expressions.

So when I review I advise, as per the spec, that expressions contain a single side effect.
The go team recognise there's a fundamental problem with it, otherwise they wouldn't have created dep and vgo [1]

[1] https://github.com/golang/go/issues/24301
At GitLab we work async by default. But we also learned that video calls are great for bonding and solving complex problems. We don't use video calls for presentations or status updates. The exception is functional group updates that are recorded for the people the can't attend and that spend a lot of time on questions.
> Microsoft is not paying $7.5 billion for GitHub for its ability to make money (its financial value). It’s paying for the access it gets to the legions of developers who use GitHub’s code repository products on a daily basis (the company’s strategic value) — so they can be guided into the Microsoft developer environment, where the real money is made.

This reaspm makes the most sense to me, re: why Microsoft purchased GitHub.
Dumb question about this malware... with so many infected routers, why was this not noticed sooner? Just monitoring incoming/outgoing data should reveal that the routers are "calling home" at some point, yes?
I got Silence on the Wire after reading your comment. Let's see how it is.
If a union is so good then a company would not be able to hire anyone outside of the union because everyone would want to be in the union.

It’s a voluntary system. Anything else is just tyranny.
We have performance reviews not annually, but every few years.

My last review, the head of our division got really angry with me and gave me a very negative, punitive review.

What I am infuriated about is that never in that few years did I receive any negative feedback, and I tried to do exactly what our subdivision had decided as a group to do, and what the immediate superior had wanted. My last review was glowing, perfect. So I go from a perfect review to being treated like a failure, fireable, with no negative feedback in the interim.

Imagine if you in your area had discussed things, come to consensus decisions, you were willing to do everything asked of you, and then four years later someone higher up singles you out and yells at you for not doing what you're supposed to etc. As if you've been getting feedback that whole time.

The worst part of this is that I know someone in our area is close friends with this division head and basically complains about everyone except one person in our area.

So now I have this negative review, as if I were just being lazy, even impaired in my duties, and not doing my part when the whole time I just thought I was doing what we were supposed to.

It's depressing as hell to me, and also angering.
Maybe it is for them, but `node -r esm` is what I'm going to do for now.

I'll probably start webpacking the backend soon instead, but I'm sure as hell not going to rename every single file in my codebase.
No, the real point of the article is that "according to the OECD, "the US system [is] progressive." The most salient feature of the U.S. tax system is that "middle-income US households face unusually low tax rates"--i.e. the system is highly progressive.

The U.S. tax system is progressive well into the top 1% of income earners (by contrast, Germany, Sweden, and Denmark have a relatively flat tax structure after about 1.5x the median income). There is a lot of focus on tax breaks for the top 0.1%, but 90% of U.S. income is earned by people outside that group, and 80% is earned by folks outside the top 1%.
what's the right amount? 2 group calls per week, each under 1h?
Thanks for the clarification. The official Helm charts go through a thorough community review process. We (Bitnami) are committed to making high-quality, up-to-date Helm charts. You can check https://hub.kubeapps.com
What's a COLA?
Larry + Sergey + Eric have majority voting control, though. Each class B share (which they hold) counts for 10 class A shares and an infinite number of class C shares when it comes to corporate governance.
A flat tax on labor income, with a cap, is a typical model for Social Security in Europe. E.g. France, Germany, etc. Ours is more progressive because the cap is generally higher.
A lot of military spending is building stuff to blow up. I rather pay people to build windfarms and trains.
I would be the last person to say that there isn't a lot of waste in defense budgets. But you can't spend zero on defense. And the United States also defends all of NATO and a lot of Asia as well as certain other allied countries. Let's say you could somehow shave a few hundred billion out of the budget without materially impacting our defense capabilities and obligations. That's not enough to fix our bigger problems with entitlements.
Minor note, CICS (and impls with screen divisions) implement psuedo-stateful interactions similar to http with tempoary storage queues in place of sessions. The 3270 client is textual as opposed to graphical like html of course.
Those "labor monopolies" were negotiated voluntarily in environments that were already actively hostile to unions. Right to Work laws interfere with the right to association idea that libertarian capitalism champions as a absolute good.
ActiveRecord isn't really an ORM. It's a way of building queries against relational data, and associating some methods with the tuples you get back (which might not even be full rows). It also has a bit of support for C, U and D, but it's strongest in R. Although many queries won't fit in its model, it's trivial to inject snippets of SQL where needed.

What it is not is a way of mapping databases to models. The models pretty directly model the database, rather than the other way around. Quite different to something like JPA.
It makes a huge difference whether you can pre-populate a new network with a list of your friends, as it makes your friends' discovery possible.

Imagine, which Google+ launched, how things might have gone if 5% of Facebook users could have moved their own social graphs to G+ with two clicks of a mouse. If everyone had 100 friends, and those friends were uniformly distributed (all stark simplifying assumptions), then a huge fraction of the global social graph could have been moved to the new network by a small fraction of the users.
This issue is not just a lack of learning from past failures, it's an active issue that is systemic to web development, especially node. Everyone wants reinvent the wheel rather than supporting a similar, already existing project. I don't know if it's that everyone wants to be the lead on something or if they all lack group skills, but there is no reason we need dozens of similar, partially functional libraries. I can barely, and I mean sooo very barely get behind the fact that all of these SaaS companies need to create their own versions of frameworks, but it amazes me just how many square wheels there are in the web community. It was one of the major reasons it took me so long to start doing full stack development, just way too many cooks all wanting to make almost the exact same meal, only theirs is more superior.
Recently switched to vscode but I can't replace datagrip. I've been able to use SQL operations studio but it's simply not as good
If the military industry became
unemployed, social security would get a lot more expensive.
> Disadvantages
> Scares investors - Scares some partners - Scares some customers - Scares some potential employees, mostly senior non-technical hires - Onboarding is harder, first month feels lonely

We do a full remote policy at SerpApi.com, however I found this disadvantages list a bit dishonest, they are more way numerous and important, the most obvious are missing real human contacts (and it doesn't get easier with time), and harder life and work separation.
This why I love Java so much. Take a look at what Spring Boot does for me:

- Routing is done in two lines of code:
@Controller
@RequestMapping("/myroute")

- Cookie and body parsing - no need to write any code to do that, I just have method parameters and all of the data flies in. Whant a validation? Only one keyword on a method parameter - @Valid. Custom validators are supported as well.

- Session management. It just here for me and does the right thing by default. I can replace storages with custom implementations but by default no code is required from me.

- MongoDB integration - Spring Data MongoDB and you only need to define interfaces using naming convention. The code to access the actual database is generated for you.

- Spring Security supports multiple authentication mechanisms and gives you neat DSL to configure it.

- File system access kind obvious thing.

- HTTPS and HTTP2 support provided by Spring MVC as well.

- Compressions support - it just "server.compression.enabled=true" in your config

- Logging - slf4j + logback come with Spring Boot and there plenty custom appenders available to put you logs into logstash/splunk whatever

- Referrer spam filter - not sure about that one but CSRF protection comes OOB and enabled by default.

- Multiple tightly integrated template engines to chose from. Zero configuration code as well.

- Static content comes OOB and enabled by default, just put your stuff into resources/static.

I mean yeah, modern webapp is a complicated thing! So whenever I see somebody trying to do anything "not bloated" it means that I end up writing low level code that has been written multiple times again and again.

The other day I was trying to code a simple thing in Clojure because I love Lisp. Well, it's just embarrassing. I got to simple page showing stuff from Postgres and the boilerplate/business code ratio was at about 70%. Manually configure connection pool, manually start it, manually prepare your component systems, manually mention all of the dependencies for components, manually configure template engine, manually enable static resources support in ring, manually configure and enable session support in ring. Then we come to authentication and don't even try to sell me Friend. EVERYTHING is manual. The only good thing was "environ" which did the right thing but again with "bloated" Spring Boot it comes OOB and I don't need to configure it!

If you don't use something "bloated" it only means that you're writing code yourself, again and again.
Personally, I do not, because they make decisions like "I should have to pay less taxes so I can have even more money and I do not particularly care that the trains are barely running and constantly late, since I never take them anyway."
I've used Phabricator along side github; you can have it track any external git repository, and use its task tracking and code auditing tools, both of which are much better than github (Github's CI integrations are much better though, fwiw).

The value added by github is primarily that you can get drive-by patches submitted because it's become the tool that so many developers both already know how to use and already have an accountse. Phabricator is much more focused on providing value to set teams working on a project, and it does that really, really well.
Is there a consensus on the cancer risks of fermented foods like kimchi yet? Last I saw, some types of kimchi were associated with stomach cancer while some were not, but I'm not sure.

Lately I do a lot of pickling with vinegar/salt/sugar. I'm now addicted to pickled daikon. If I could only find a container capable of restraining the smell...
It’s silly to get so hung up on these words. We all do the same things.
Enh, the Dragonlance novels were RPG tie-ins published by an RPG company. I'm not sure that counts.
> This stuff isn't relevant at all to the talk - he never talks about npm or anything to do with package managers but instead how node does imports etc.

He does have it in his slides.

Slide titled: "Regret: package.json", last 2 points:

> Ultimately I included NPM in the Node distribution, which much made it the defacto standard.

> It's unfortunate that there is a centralized (privately controlled even) repository for modules.
Came to the thread to say this. The site loses a lot of legitimacy by glossing over very real tradeoffs to having a fully remote team.
Then he should have blown the whistle no? I mean his title was CSO. Wasn't there a moral imperative there to notify millions of users who were affected? I don't think its a stretch to say by participating in a cover up you are complicit even if the original decision wasn't yours.
Dakara Nanda?
I've gotten the feeling that flowcharts used to be considered quite important by lots of coders, while today they are only used in particular subcultures. A flowchart is sort of an ungainly artifact. It repeats information that is in code, but is more difficult to produce and save than code is.
What about health insurance? USA's privately funded health insurance is equivalent to flat or regressive tax, not a progressive tax.
> as a Millennial, I don't expect to ever see a cent of Social Security benefits.

Even if the Trust Fund is fully exhausted, beneficiaries will see a sizable fraction of full benefits from current payroll taxes.

The only way this doesn't happen is if the program is modified to affirmatively deny people already-earned benefits, which is probably less politically viable than fixes that would protect full benefits even with pessimistic projections.
Download the latest Yaoi Manga and BL Drama CDs for free. Daily updated website.