https://monkeyuser.com/2018/...

@kiki ??? Where did the dreaded butterfly switch come in the conversation?

Perhaps Dell is still copying Apple mistakes. They have a capacitive top row on the XPS. So would not surprise me if they use butterfly too. But I've never claimed the use of such a thing.

@kiki you are correct that it's membrane but it's a specific type of membrane that in my experience has gets broken more by an order of magnitude. Usually user (or cat) mishandling. Trying to clean debris underneath.

Most of the time it's the key cap part that clicks on that breaks. The scissor plastic itself can what be bend beyond function too.

My experience is based on being a systems admin that needed to maintain all the companies hardware. Just about all keyboard issues where scissor related issues and not the membrane.

Apple != Only keyboard manufacturer. They are still made and used

I've had some keyboards fail on me. A very flat one. Think they used scissor switches. A single membrane one failed (one key didn't pop back up). But that for sure was a one off.

Another failure was just by yuk caps. Was with some sort of rubber feel and that turns to sticky goo (it's a common coating, now I know you can fix it with alcohol but it will be shiny textureless).

I've had a single switch failure on mech keyboard within two years. Got a replacement under warranty was actually an upgrade. This was in 2018. Still use this as my main board almost daily.
My first mech keyboard I keep at the office and have that since 2016 (bought it for the office when I had to be there every day).
Both are cherry MX brown non hot swappable. But the one at home is vastly better (nicer build, less key wobble).

It's worth the investment for the feel to me, they last long and can get cleaned better.
I do agree that other than cheap plastic implementation membrane keyboards can last very long.

@kiki lol

I do like typescript when a codebase is larger on business logic/concepts. The type system still gets in the way some times but it aids the development more often (auto complete, suggestions, interfaces say what they need).

I've never used it in a private project by choice.

@glowFX this is the way

Ah that kind of passthrough. So an AR variant. Sounds cool.

We even had a company policy to do that for all numeric id JSON responses due to the size limitations. Same for some representations of monetary amounts to prevent floating point calculation errors.

There can be good reasons for it. But in isolation all solutions look odd.

What's a pass through shader?

I've actually yet to see a place where that is not the case. Sure some actual output performance is required but the highest pay always goes to the one that projects themselves the best. Never the quiet workhorse.

I feel that language preference is indeed a thing that is sorely overlooked.
I'm in the Netherlands and fully Dutch but hate Dutch music. Can't turn that off in any music streaming service.
Same with books, I love reading the original English texts or translations to English (they are generally better). However it's super hard to find the English versions for me and all browsing/adds are Dutch versions. Nowhere did I even set that I speak Dutch.

Also Belgium is weird. If I would live there I would for sure speak both French and Dutch.
My French is really rusty and noticed that Brussels is basically French only with here and there someone that also speaks Dutch.

@Tounai nothing to do with the game at all.
They are all steam phishing scams.
The only thing that is CS related is the value of in game inventory (skins). Plenty of other games with transferable in-game inventory that boosts the value of a steam account.

@Lensflare lol I see I'm too late.
Edit: @tosensei , like really late.

Yes

@CaptainRant the way of working is something you bring up in retros, other learnings too. But for summer reason a lot of people are stuck with the idea that a daily scrum or stand-up is about 3 questions and that's all the communication that is needed.

I don't have a doctorate in agile or scrum however I've fought hard to make teams operate the way that works and I like. It's more kanban style and no freaking status updates. We schedule a meeting when we need it with people that makes sense. Nothing in the agile manifest is against that quite the opposite actually.

What you guys are doing is twisting it like terrorists and politicians twist religion.

@CaptainRant don't know why you reply to me and probably downvoted. You are making exactly my point...

The complaint in OP should be handled in a retro. They are just going through some weird burocratic motions and use that as an excuse to not function as a team or have any meanings for making important decisions (as a team).
I don't care what methodology™ you throw at it this is never the goal.

Nothing you described has anything to do with agile™

Unless they block something its not supposed to be in that meeting anyway.

@Demolishun not specified but this is specifically about pesticide application. See my comment on the post...

Stop spreading lies please and do some actual research. When reading your post the first thing that comes to my mind is well that looks out of context. Where is the bloody context!

EU is wise enough to not allow caffeine as a pesticide. That is the context. It has an effect on humans so it's considered harmful as a pesticide. This means in the EU you won't stay awake eating a few carrots all the sudden.

https://euronews.com/my-europe/...

What an elaborate way to say that sugar is bad for you!

@electrineer that is not the problem. The problem is separation and a switch for multiple versions of the app (both actual versions as different platforms). Is it account level. Geo IP level or even both.
If the platform already supported displaying a regional error message (which is quite likely) and there are already tools in place to identify regional traffic it would indeed be fairly easy.
If not it's a lot harder. Especially if you need to block US accounts not just IP/ISP based traffic origin.

The mistake you made here is believing it is your taskbar.
Every part of it has been filled with a promotion at summer time and will again.

If not friend, why friend shaped?

@Hazarth I still like it a lot too. It's easy to debug and often feels a bit like a scripting language and comes with all the tools you need by default. Super low maintenance. Sometimes they do take the simplicity part a few steps too far though.

Yeah there are no enums. Go has plenty of quirks but it's highly effective.
Rust has a really nice enums implementation but you will be fighting a lot of the language at the beginning.

I know about performance but really can't be bothered by big O notation.
So far I'm the one fixing all the issues. Most of the issues are race condition or database representation related.
All my coworkers seem to know about big O, but none of them can seem to grasp the rules of synchronization. Understanding the implication of things is far more important than anything any school has to offer.

It for sure had a place but for most things I find go and C more useful. Quite some C++ use cases where Go just isn't good enough Rust makes sense. That is why I do think that an application like a browser makes sense to write in Rust.

The cult/hype peak may come to an end. Go had the same over hype bs. Now I see it used too little where it makes sense. Paru for example should never have existed for example Yay could benefit from the extra development that went into Paru, Rust adds nothing here. Network and pacman are the limiting factor.

@Lensflare Actually it is not when done right.
SuperDuperAbstractFactorySingleton
is harder to read and distinguish from SuperDuperAbstractFacilitatorSingleton.
Contains way more crap you read before you get to the unique descriptive part than say Facilitator.

The closer the variable is to it's usage the more context you have and the shorter you can get. This translates to his deeper the code and the smaller the function the shorter variable and function/method names can be.
The opposite is also true the further away and more exposed the more verbose you need to be. This is because you don't have the context and in need of some descriptive naming. Still just enough so you can dirive context without making it a chore for your brain to process.