HackerTrans
トップ新着トレンドコメント過去質問紹介求人

npstr

no profile record

投稿

Stop talking

gurkan.in
56 ポイント·投稿者 npstr·7 か月前·60 コメント

コメント

npstr
·15 日前·議論
ears have to be shown to camera to confirm no devices inside

own calculator not allowed, there is one provided by the software that must be used
npstr
·16 日前·議論
Seems easy to counter all of this. I study at a German remote university, and they require, next to the front camera, a second camera to record the screen + hands and arms of the student while taking exams, and before the exam starts a complete video of the room, below desk areas, ears, etc. I don't see an angle how to reliably cheat in such conditions, and have seen nothing mentioned by any other student. So I would say it's up to the university if they want to allow fraud like that...they could easily stop it.
npstr
·先月·議論
i and j etc is bad though, but for a different reason than usually claimed. it's suboptimal because it's hard to search for. just use ii, jj, kk, etc
npstr
·2 か月前·議論
[flagged]
npstr
·3 か月前·議論
how about "Maschinensturm", a German word closely associated with luddites?
npstr
·6 か月前·議論
What are you basing this on? The announcement literally says the people doing the work want to focus on the work and not the bullshit, so they are firing the bullshit people.

> Engineers in particular have expressed their desire to focus their time on engineering, without being hampered by slow process flows, and restore the fast-moving culture that has made us so successful.
npstr
·6 か月前·議論
Not nothing - they are doing bullshit.

> Engineers in particular have expressed their desire to focus their time on engineering, without being hampered by slow process flows, and restore the fast-moving culture that has made us so successful.
npstr
·6 か月前·議論
Yes, they absolutely are the bad guys, if they are the reason that the Engineers - the ones actually making the product - are unhappy. Did you miss this part of the announcement?

> Engineers in particular have expressed their desire to focus their time on engineering, without being hampered by slow process flows, and restore the fast-moving culture that has made us so successful.
npstr
·6 か月前·議論
Sorry, but the empathy is misplaced. These people working bullshit jobs are dragging down the whole organization. If bullshit jobs are allowed to proliferate, they risk the even larger number of jobs (and families) of the people doing the actual work.
npstr
·6 か月前·議論
https://archive.is/yRObl
npstr
·9 か月前·議論
> Why aren't things this way?

They are in my JetBrains IDE, IntelliJ. Just use proper tools instead of toy text editors? It's free and Open Source even.
npstr
·10 か月前·議論
I had some RSI at the start of corona from too much home office + gaming, what actually helped was getting a trackball (Kensington Slimblade Pro) for $work tasks.

Tried a Moonlander and hated it. My hands don't work with ortholinear. And I hated having to learn layers and layouts. Besides I have a real job and I use a proper IDE so I need my F keys, I like to use the Home/End/Page Up+Down keys, I learned to use the numpad efficiently, etc. I think most of what is told and sold in ergonomics is snake oil. I don't believe ortholinear is any good for it, and minimizing movement also seems really questionable to me. I'm working with comfortable 30-40 wpm and am still one of the most prolific and productive engineers at $work, typing speed is not important for many jobs.

I would like to continue be able to use regular keyboards efficiently and with little annoyance. Too often I'm traveling and stuck with the laptop keyboard. I have to accommodate Linux ($work), Windows (gaming), Mac (personal projects, open uni). That's already challenging enough to get these have similar shortcuts. I use a keychron K5 pro that supports all OSs. I can work efficiently in all situations, with all OSs, with just a single screen. Having a more specialized keyboard (or otherwise setup, like relying too heavily on multi-monitors), wouid overall surely be detrimental, during the times I could not use it.

What I've learned to avoid pain: Wrists should be straight. For me, a slim keyboard helps to achieve that, flat on the table. Hands should have some room apart, open chest. Small keyboards are bad for that, you'll want a 100% one, or a split. Do some lifting, have some muscles. Try a trackball, you might love it. Switch how you are sitting. The best sitting position is the next one. Get up to think, go for breaks. Don't overly specialize into some local/global optimum that is a moving target over your lifetime. Use defaults. Mostly boring setup with some minor personal tweaks can go a long way.
npstr
·10 か月前·議論
It looks like you're not up-to-date, ZGC has pauses on the microsecond dimension. Even since before ZGC was added, there are open source libs for HFT that optimize allocations to avoid GC: https://github.com/openhft =3
npstr
·10 か月前·議論
The Readme has a section for the raison d'être for it compared to the original ANTLR: https://github.com/antlr-ng/antlr-ng?tab=readme-ov-file#futu...
npstr
·11 か月前·議論
Why can't they bill for it? It's not like they are losing money on it, it's simply getting priced into the billable services they provide. Utilities are usually monopolistic, so there is little incentive for them to fix this.
npstr
·昨年·議論
Android started doing the same thing to app icons many years ago, and I hate it. Luckily there's custom icon packs that help solve this but it's annoying to figure out how to set up on each new phone. Increasingly UI teams seem to be stopping developing interfaces for humans. Same has e.g. happened to icons in IntelljiJ IDEA, now only usable with icon pack plugins. All these UI teams need to put on mandatory HCI courses or fired.
npstr
·昨年·議論
https://archive.is/44KfE
npstr
·昨年·議論
In Germany it just means it's a bad place to have a career in. Thankfully most HRs will happily advertise it in the job description making it easy to dodge.
npstr
·2 年前·議論
No, what he says is "when we write software there are bugs, so we should write less software".
npstr
·2 年前·議論
I'm sure there is plenty of movement visible on all kinds of bridges. We also know that all bridges will fail eventually, so the real value is having a more or less exact prediction _when_ they will fail, not a "we totally saw that coming" after the fact.