Recent submissions

Comment · 4 years ago
Before I start working on a project, I spend a couple of minutes to read and understand the logic of the current code base related to the change. By doing this, it naturally reminds me about the language syntax, the framework, the project convention, and the team's best practice. If you do it regularly, you will feel it more natural. Most of the modern languages' projects are easy to identified the scope of changes. Don't pay too much attention to the languages syntax, but rather to the logic.
Comment · 6 years ago
Same to me. I store the note folder to a private gitlab repo, and write a bashscript function to commit and push the note.
Comment · 8 years ago
How Google works https://www.howgoogleworks.net/

Those ideas and principles of building a successful Google, from making great product, build the great culture and hiring the smart creative people.

Comment · 8 years ago
Did she mean daily rate? I wonder if a junior ask for this rate, of course the company has no chance to afford a senior dev.
Comment · 9 years ago
Comment · 10 years ago
I totally agree with you. We tried, but things aren't expected
Comment · 10 years ago
I think you have no trouble with typing, because you care too much for your code quality, it makes you slow. However, you are doing good thing for other people - who will work on your project and for yourself.
Comment · 10 years ago
Checkout Rack (https://github.com/rack/rack) and Hanami (https://github.com/hanami/hanami).

I myself learn a lot from these projects. The code is clean, with good tests and documents.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton