I’ve bought from the Keyboard Company before. They have a large range of ergo keyboards. The Keyboard Company | Keyboards & Mice Sales Distribution[^]

Love it!

I totally get you. I started coding around 11 - I’m now well north of 50 and I’ve probably thought about coding almost everyday since. It’s obsessed me, it’s a beautiful activity that is also hard, frustrating but rewarding. I’ve often blocked for different reasons:- - the requirements were vague - deep down I didn’t think the feature was valuable (to the user) - I didn’t know where to start - I was burnt out (often because of the above times 100) Depending on above:- - go and do something else (cycling, swimming, etc) - go speak to the (REAL) end user. It will either give you purpose or prove its not valuable - write a failing test for the new feature. Then make it pass! - write a todo list for the feature. Here’s the thing, though, make the next action really, really small so you could just do it will zero effort. Then make the next task that small. Keep going (read “getting things done” for more on this) This should get you going. But remember to look after your mental health x

Shokz OpenComm UC is supposed to be the new hotness.

I’m still getting over WIN+V paste history.

If you don’t like more succinct code I would just stick with COBOL

Well, I miss having the taskbar on the top, where it should be…, (Ducks for cover)

Btw, I don’t use a separate diff tool much these days as I’m usually running SublimeMerge which is a super fast Git GUI with built-in diff/merge. Again, I bought my own licence because its too tedious trying to justify a work purchase.

A colleague recommended BeyondCompare (paid) ten years ago. It was by far the best I used so I bought a personal licence and have used it since at every employer. At the time it was two features that were unique at the time:- 1) manually align two chunks of code. Useful when only you know they are related 2) isolate a chunk of code that has been matched to something (but you know has no match) Both features are useful because a diff requires info that is no always deductible without input from the developer that made the changes.

You’re basically doing all the hard work that any self-respecting dev should do with testing so shifting to TDD would be no effort. But I would watch Ian Cooper on YouTube, “where did it all go wrong” and maybe read the best book on it (Kent Becks) as many have mis-represented his words of wisdom. TDD will speed you up if done right.

If you’re short on staff I would say no as a good dev will cover the analysis. This is where I like to be. If you’ve got the staff then I see BAs as a specialism: developers can spend more time on the technicalities whilst the BAs can dig deep on the “whys” around specific business practices, unravelling complex processes that as a developer you might find tedious. However, BAs and Devs need to both attend the core meetings to that BAs don’t become a go-between or worst, a poor information conductor ;)

Sprint #2168 : complete

At the end of the day, it’s a way to implement your public interface to the world without your clients being exposed to the details. You have many options to implement that interface; code directly in the class, delegating to others (composition) or inheriting it. Imagine parallel universes, there is the public one that clients exist in and another that the non-public stuff lives in. Both (potentially) have a need for inheritance either to represent a natural taxonomy (CheckingAccount isa Account, etc) or for reuse (Account inherits Persistent, Equatable). I say “potentially” because out of all the ways to implement your public interface, inheritance is by far the worst in my opinion - it’s the road to spaghetti code ;).

Works in outlook too when you are typing the to: address, allows you to delete old recipients