wyaeld

Tailwind UI is the component product.

There is a distinction between being able to access the source code, and a tool giving it to you without any context of the underlying license it is governed by.

Good teams still document these. Amazon is apparently a leading example where the documents are considered the source of truth.

However many organisations have limited technical leadership enforcing quality, and management layers not willing to invest in these assets.

Unfortunately some 'modern' practices are being interpreted to make the processes like Agile the most important thing, and reducing the importance of things like code/system quality and knowledge management.

Having a good technical writer pays dividends

The author seems to be using Monolith and Monorepo interchangeably, when they are not.

This sentence "With that, Wayfair decided to split the monorepo into smaller microservices" makes little sense.

The main reason most people have monorepos in the first place is because they have smaller microservices, and to facilitate working on them as a unit.

Google collects immense of data about people's actual visits. Backlinks used to be a proxy for how authoritative things were You don't need the proxy when you have the record of where people actually visit.

If it made over $1b in a year previously, and had such insane load times, its very plausible this bad coding has cost them north of another $1b.

Probably ranks pretty highly up there in terms of damage to company financials, due to a lack of care.

Very few large organisations, and zero distributed ones like a collection of multiple government departments, can turn around a massive collection of security fixes in 2 weeks.

I believe Google's Security team usually gives vendors 90 days before they go public.

ES had a business model. It was open-core, but with critical features like Security and Access-Control hidden behind their paid support.

The core disagreement was that Amazon (and many other contributors) wanted to add that to the base distribution, and Elasticsearch fought them for years on it, deliberately breaking any community plugins that got a solution working.

Enough blame for the current situation on all sides.

The whole point was that the Intercept had specialist security experts on staff who know this, but the reporter rushed the story, told his own sources in the intelligence community critical info without realizing, and never actually spoke to the Intercept security team.

The fact that the Editor-in-chief did not ensure their own processes were followed for an NSA leak is a failure.

Plenty of us 'good engineers' aren't anywhere near that proficient in frontend either. I can build great backend systems, that's where my interest lies. I can't do CSS like this even with months.

I would expect their market is the group of professionals for whom doing that is simply not worth the time.

When your job is delivering high quality UX and there are always more apps to build in the pipeline, having someone give you a library of useful components works.

I have licenses for probably 4-5 of these, and they've all saved many hours of time, and resulted in avoiding the cost of a dedicated designer.

easiest way is just start experimenting with GKE on google cloud, and see if it has value to you. Don't bother trying to deploy and manage it before you've kicked the tires.

Out of the box its quite good, depending on what you are doing, once you have cert-manager issuing you free certs, linkerd managing a service mesh, and stackdriver giving you an entire ops stack, its a bit hard to go back

No idea what recruiters look for, but when I'm part of a hiring process I'm particularly interested in evidence about how well a candidate communicates with other people, whether presenting their ideas or discussing options.