pnt12

I don't know a lot about monitoring, why do you say pulling is an anti pattern?

My understanding is that with the push pattern you submit a metric when it's available, with the pull pattern you make them available via an interface.

I've read the first is not as performant, as it leads to submitting lots of metrics. Although I can think of an alternative, which is storing them and pushing batches periodically?

Older generations always critize younger, that has little to do with inflation and price sensitivity.

The boomer doesn't like avocado toast, so they don't understand how someone would pay money for it. But it's likely they are also buying stuff milenials have no interest in.

But does it result in better quality of life? Maybe competitiveness is not the best target to optimize for.

It's not that they lack moral character - is that they don't exercise it.

The whole system rewards maximization of profits, and all else is an up hill battle.

Won't someone think of the shareholders?

This denial of responsability is a cancer on society. Poor devs, they can do no better because their manager ordered them to. Poor managers, they can do no better because they must reach their OKRs. Poor CxOs, they can do no better because they must please the board. Poor board, who must maximize the returns of the shareholders. Poor shareholders, who just want their retirement funds.

Anti-terrorism and authoritarianism go hand in hand, that's been clear since 9/11.

The problem is that government us terrorism scaremongering to justify erasing citizens rights. It's completely valid to be anti-terrorist and prefer alternative choices to fight it.

For example, in my country, both polices and tribunals are severely under provisioned. I'd start with imroofijg those budgets before passing surveillance laws.

People keep themselves busy (or soon they're out of their job). When there's no high or medium priority studs to do, people move to the low priority and do it, even if useless.

The good old trickle down.

I agree with the sentiment, but a there is a caveat: not all documentation is created equal.

There's incomplete documentation. There's API documentation without examples (ie specification but no example/tutorial). There's outdated documentation!

I can also say that I started studying SQL by reading the docs for mysql, and after an hour I was still stuck inside INSERT or SELECT. Reading about all use cases in detail was not useful to learn a first approach to the queries!

So I'd say that this "truism" isn't always true. Sometimes the docs suck or don't provide the info you need at that time.

Good question: I see one way it may work and another it may not.

I think the profile of their users is less diversified: mostly tech savvy people. "Normies" are using those vpns advertised in YouTube, or not using any at all. This may result in similar interests and lower the number of unique queries.

On the other hand, we may produce more unique queries than other people: who will receive-use the cached "how to fix ValueError on main.py:67"?

They explained it:

> Regrettably individuals have frequently used this feature to host undesirable content and malicious services from ports that are forwarded from our VPN servers. This has led to law enforcement contacting us, our IPs getting blacklisted, and hosting providers cancelling us.

https://mullvad.net/en/blog/2023/5/29/removing-the-support-f...

All companies depend on their customers, that's not a reddit only thing. If Coca-Cola pisses of their customers, they'll go to Pepsi in the blink of an eye.

I think type hints help a lot. A codebase with classes and type hints reads much better than one using ad-hoc dictionaries for every data structure.

But on the other hand I don't really like Go, so maybe it's different languages for different tastes.

Not the parent but pipenv is decent, poetry is even better:

- clear separation of dev and production dependencies - lock file with the current version of all dependencies for reproducible builds (this is slightly difference than the dependency specification) - no accidental global installs because you forgot to activate a virtual environment - (not sure if supported by pip) allows installing libraries directly from a git repo, which is very useful if you have internal libraries - easier updates

>They want the highest resolution so they can see their 10 gram progress when dieting.

Do they? 100g is already quite granular, and you can lose that in a day.

I have two scales which are giving me different measures - I've been weighting myself and assume I'm in the middle of both. It's a bit annoying, but works for my goals.

You're exaggerating.

Requesting for people to communicate more in group chats instead of direct messages takes 5 seconds.

Scheduling regular 1:1s with juniors keeps a tight feedback loop. Schedule it once every x weeks and there you go.

Counter argument: there's lots of ways to share knowledge remotely, some people just aren't used to it.

Learning: presentations, pairing, questions via messages, asking for a quick call to clarify something. Also: document your shit.

Ideation: set up ideation sessions before tackling a ticket. At the end of a daily scrum, ask people x and y to stay and trade some ideas.

Also: switch it up?

I propose using Facebooks old name and switching one A to I (iThings?). Then we could call them MAFiA.

As far as I understand, it's mostly the weights. If you only have the models, you're still gonna need to get a massive amount of training material, huge costs for training it and fine tuning the hyper params until it works.

Hmmm... I'd day restoring a bad review would be even more suspicious. Let them come naturally and don't delete them - unless the company reconsiders the benefits of premier, that is.

> that anyone realized

Not to be pedantic, but lots of people "realized" (or predicted) this, myself included.

He promised something, charged for it, and had little to show for. To me that's a big mistake, not little "ooopsie shit happens".

And it's not clear this will be fixed 10 years from now. Experimental research often fails in some stage between research and production.

On the other hand, consumers have little control over businesses. I'd be fine with eco friendly delivery, eg more wait time to minimize trips in the neighborhood, electric cars, etc. Most of the time I'm sitting on a full online cart for days, and removing stuff I don't really need until I'm happy with the order: I can wait.

But where's that option?

I just take my rare (and voluntary) office days as socialization days: more talking, longer lunch hours, longer breaks.

Its fine once in a while but I don't wanna get back to WFO again.

For some, it's a pay cut, in money and free time. It's a valid reason they'd rather change job.

Relevant xkcd: https://xkcd.com/538

If encryption is illegal, you are suspected of having to encrypted data and don't provide the keys, the police won't be puzzling about what's random or encrypted bytes: they'll interrogate you, abuse you and throw you into jail.

I also think there's something to it: each person is different.

I've smoked and quit a couple of times, and still get urges to go back sometimes. Meanwhile, I know people who casually smoke once in a while and don't get the habit.

I have mixed feelings about this.

One one hand, I have experimented with co-pilot and this was my experiencerience - great when it worked, easy to fix when it didn't.

On the other hand, I worry people are not ready for this - get these magical answers and go double check them. Most people don't read the Wikipedia referenced they just trust it - are they going to double check LLMs?

It is.

OP is stating his love for the worst parts of games. This would be like someone saying they love pages filled with ads, chat bots, pop-ups, auto play and scripts which take seconds to load.

I hate when a long technical document doesn't use BLUF, ie omits a summary at the start with the main topics.

There's too much info on the internet, and even in internal documentation: if I have to read half the thing to understand if it's relevant, I'm gonna spend most of my time on irrelevant stuff.

This is a problem with asking engineers to document without having a writing culture. I've seen it happen: once it's written down, that's it: it's documented, great work! But we should treat it more like code, with clear divisions of concern s, scopes and even refactors when needed!