> 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.

> 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.

> 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.

Comments URL: https://news.ycombinator.com/item?id=46137845

Points: 56

# Comments: 60

They are in my JetBrains IDE, IntelliJ. Just use proper tools instead of toy text editors? It's free and Open Source even.

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.

Forgive my judgy wordings in the direction of seniority...our org has (had?) an issue where complexity is rewarded over simplicity. Some senior people here all they could do is build something so clusterfucked noone can understand it. Funnily enough, this project was originally launched to replace a legacy system noone was able to (or unwilling to) maintain.

The security concerns about actuator I cannot subscribe to either. Why are your endpoints exposed to the outside by default? Why is the management port reachable from the outside? Why are devs not reading the docs and only enabling the endpoints they need?

The magic annotations part can definitely be a problem. Would recommend to stay away as much as possible and keep that simple. Only use it as a last resort, but boy can it be powerful. Need your own request scope that is bound to transactional commit/rollback? You can have that to for example only send out side effects when the transaction succeeds, or to build transparent caching solutions on request scope.