LolNoGenerics

I don't think everyone leaves with the next best salary upgrade if you pay fair. Leveling up a junior should be rewarded in time. Part of the mentoring is to teach them how to fight for your upgrade, right?

Good culture is good, but no culture fits all personalities.

In the end you probably have to accept that some portion of mentees will leave and try to minimize the rate.

What I would be afraid of that grown up juniors may get stuck in their learning environment and remain junior for way too long.

You started out with the claim that your database is fast, but you added almost no info to support this claim. Don't get me wrong but if you remove the initial claim the article would be more trustworthy.

> The purpose is to broadcast your view of your priorities, so interested parties can ask that they be adjusted.

Concrete team stories are usually quite clear. OKRs force you to encode a bunch of them into objectives and key results. This produces utter nonsense if the duties and opportunities are generic or fragmented. Not every team can write a clear OKR which makes it obvious what's happening, especially if you servicing multiple departments.

Propagators of those techniques also tell you that sometimes there is no help. I.e. completely irrational positions or mindsets, as well arguments that are already set with hostility.

Plus the mercy of 3d card companies to make their linux driver's suck less.

If you want transaction like behaviour you can simulate it. Not sure if that is even remotely a point with Web APIs.

The overlays totally ruin this site. Help!

Sql databases are usually behind an application layer. Still they can suffer from RCE. Sqlites model is no protection.

Now I am intrigued to make a minimal snippet that creates a histogram of loading times.

To mock about the doings of others is easy. Plead me guilty. But there are rights and wrongs on both sides. Usually.

My theory is that engineers are often stuck in a filter bubble. Especially newer engineers. If you read all day about microservices and SPAs, there is at some point no place for something else. But classic web app achitectures are still doing very well. At a common scale they do things better with less complexity. The point is that they aren't very heavily discussed anymore. Most problems have been discussed and there are solutions for it. For me it is hard to argue about the problems of modern approaches. Not because I don't have any arguments, but because mostly the response is that we have to throw more code, hardware and architecture at it. It works for FAANG, why argue?

All sides need to pay more respect to things that work. And we have to set context when/where/why it works.

After the ausus EEE series became hip I tried a random cheap product which was supposed to be a media center / entertainment system. It was horribly slow, running android. Even more worrying was that they rubbed remote desktop stuff under my nose all the time. I was so scared to handle any remotely personal with it that I gave up on it after 2 sessions of messing with it.

If you don't care about the money, test you luck. But I would be very careful. At least considering security/privacy.

Usual question for this. How you handle sessions? The php built in is very bad if you recycle the main process.

I think you are referring to pantheism?

https://en.m.wikipedia.org/wiki/Pantheism

Naive fainboyism as well

You missunderstood. They charge money to promote, but they don't pay for content. If I open a decent magazine or newspaper, there are ads and there is content which paid for in some way. How is google so different? Googles payment is that they give you traffic for "free" if you play by their rules. I.e. in case of wikipedia I am sure they would have hefty debt if it was fair for both sides.

Windows certainly doesn't a good job to run well on lower end systems. It got fast and reliable if you hit a baseline. Still they're hardly a competition for linux if you don't care about gaming.

Hardware retailers are just grabbing cash from average users. You cannot proof how well a system is performing so you just make up numbers and fancy words. Product series merely exists to nudge prices, they guy who buys the cheapest stuff is the biggest looser.

Cosumers would be served better if they used linux on their cheap systems. You only need a browser anyway. I used an early asus Eee PC netbook for some time with ubuntu. Yes it wasn't really snappy but it was on par with what my parents used to use. But more reliable in log term and 3 times cheaper.

But like linus said, linux won't take over the desktop market unless it is widely sold with machines out of the box.

At least we're getting paid well for watching load indicators. Atlassian should make a step forward and show funny cat gifs to increase satisfaction.

People pay to promote their links on google search. Why can't it be the other way around?

I recently talked with a peer about it and I was quite surprised. Googles move to log into chrome by default was just the tip of the iceberg what was already there. I never really noticed that google already is trying hard to merge/force all apps to run via a android login. While times have been fun and painless migrating to a new phone it is not what I asked for. It is even more worrying that google cripples their apps with this. I wonder if google one day turns unproductive when they have to untangle all that mess.

Over a decade of experience... with service workers! Nice trick, leave time travel to spock et al.

Can you imagine that it is very boring most of the time?

No reflection on the root cause? I am not into hardware but shouldn't there an redundant network connection in place or at least set one up?

Exactly. The weird thing is that you don't have to loose that JS advantages if you pull out an old school technique called progressive enhancement. If you mix that with a strict no-js first design you will achieve performance that no ultra optimised "dynamic" style can compete with.

So DDD is now a prerequiste to use OOP? Wow!

> This code may be typical of OOP in the wild, but as above, it breaks all sorts of core OO rules, so it should not all all be considered traditional.

This argument drives me nuts. A simple OOP environment can be quite easy to grasp and (mis)use. Following all the golden rules and principles that SOLID et al call for, are comparabily hard to internalize. A rookie can only fail and has to collect, choose and study all the wisdom over the years until he becomes a master. To that point he will create OO code that will break untold rules. Ruling the majority of OO code out there as "bad" is hubris and ignores reality. It is easy to do OOP wrong and hard to get it right. This imbalance is proof enough for me that we don't know what we are doing, just justifing. (Yes this may apply to other paradigms as well)

Stop excessive branching if you can use feature flags.

It's not like they want to showcase their rocket science.

He probably expected that sales would go down to irrelevant. That never happened, instead he got an absurd deal. MS is open sourcing to satisfy modders, eventually for more reach and cash. The intentions are very different and it would be awful to blame notch for that.

She has a medium blog.

The GoF book eventually did more harm then good. The outcome of GoF is that patterns are (ab)used to enforce a common code structure and a reference to the origin (book) is the legitimation for it. Code samples are good for newcomers to learn and improve, but more or less "rigid" patterns make it harder to think out of the box. The form of the solution is not relevant, just the solution. If we focus too much on the form we end up in a cargo cult. And there we are.

One of my favorite real world patterns is PRG (Post Redirect Get). While it is a HTTP pattern, it can be described language agnostic, which is sufficient for a proficient programmer to solve the problem. It also clarifies HTTP and it shortcomings to a degree. It solves a real problem, the context is clear and is useful as a pattern to teach.