unnawut | 6 years ago | on: Pay a visit to Cambridge’s computer museum
unnawut's comments
unnawut | 6 years ago | on: Pay a visit to Cambridge’s computer museum
It's one thing to see those historic computers on display, it's a whole new level seeing them running, producing heat and noise!
unnawut | 6 years ago | on: China manufactures a ballpoint pen all by itself (2017)
unnawut | 6 years ago | on: Apple disables Walkie Talkie app due to eavesdropping vulnerability
unnawut | 7 years ago | on: “No, we’re telling everyone we are using Java”
unnawut | 7 years ago | on: Why Thailand's Women Are So Successful in Business
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.
unnawut | 7 years ago | on: Sequel Pro – Open source macOS native MySQL GUI client
unnawut | 8 years ago | on: Ask HN: How to stop feeling depressed about whether you will be successful?
I know this differs between people but I'd be interested to know what sites you view as the opposite of those listed.
unnawut | 8 years ago | on: Beyond the Bitcoin bubble
unnawut | 8 years ago | on: The Casio AL-1000
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.
unnawut | 8 years ago | on: Rivals Intel and AMD Team Up on PC Chips to Battle Nvidia
unnawut | 8 years ago | on: Why TDD isn't crap
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.
unnawut | 8 years ago | on: Comcast Tries to Derail Fort Collins Community Broadband