I second this. The most amazing thing to me is that they still keep many of those really old machines and peripherals: the Colossus and more, up and running.
It's one thing to see those historic computers on display, it's a whole new level seeing them running, producing heat and noise!
This happens to me on Android as well and it has always been like this. Would love to know why a phone call needs to block all other actions except accept/reject a call.
Excuse the original title being politics-related, the actual content is not much so.
Seeing topics about gender equality and workplace diversity pop up on HN from time to time, I'm hoping this might spark some good conversation around women leadership and not on the politics side of things.
Second this. I moved away from SequelPro about a year ago once the app started to crash occasionally. TablePlus isn't as feature rich but it's fast, uncluttered and pretty stable.
Do you happen to remember how much you bought it for?
Just wondering if it was much more expensive (inflation-adjusted) than a modern one. As there are claims that products these day are made less durable in exchange for being more affordable/accessible.
Genuinely curious. I wonder how a partnership between competitors like this usually starts off? Someone near the top (i.e. mamagement) of each company say "Hey, we are behind on this. Can we borrow it?". Or their staff talk and suggest it up? Or else? Does this happen all the time but few would only make it through? Or these discussions rarely happen?
I have been attempting at TDD on and off for about 3 years. It never really took off for me. I would spend most of the time writing the tests, then implementing the code, then only to find out that a lot of my tests don't make sense, or are overthoughts that don't really add business nor technical value.
However, I think I reached my sweet spot just weeks ago. Here is my optimum workflow now:
1) Write test cases (the one sentences that say what is expected, in plain English)
2) Implement the code
3) Implement the test code
The test cases become neatly arranged in bullet-like layout in a test case file. I'm able to read through and be confident that I'm probably covering most if not all the cases that need to be covered. I'm always able to switch between the code and this file to make sure my code covered all that the tests need.
Then once the code is done, I come back to the test cases to implement them one by one, catching error by error and seeing my code coming to life. As I code now, I know I have the implementation I'm quite confident of, my tests that have business value are being covered one by one. It's been pleasure since then and I'm more confident of my code and of my time spent efficiently.