3 ms·
Start something from first principles. Examples: Instead of using a middleware between a web server and an application, write one (of course it was easier whe
by pmontra 4y ago
Start something from first principles.
Examples:
Instead of using a middleware between a web server and an application, write one (of course it was easier when I did it in 1994.)
Instead of using an IDE that magically recompiles Java and brings you to the errors, write the code that monitors the file system and runs javac, etc (2005).
Instead of using a CMS, write one (did it in Perl in the 90s.)
Instead of using a JS framework, write one (I kind of tried but no time for it.)
You'll find something that's relevant today and for your work.
There is no need to go on for too long because this approach is good for learning but bad for productivity. The problems to solve and the plausible solutions get clear pretty soon. The problem, as always, is the time.
- shakezula 4y agoI cannot support this advice enough. I recently did this with an exchange/order-filling engine in Go and it was a great little toy project. You’ll learn a ton about some things you don’t typically get to dive into when you take the “first principles” approach.
- dev_0 4y agoHow did you get the idea to work on this project? Which resources to research on etc.?
- shakezula 4y agoHonestly, I was just reading crypto news about an exchange one day and thought “that would be an interesting problem to tackle” and so I went for it. I have been meaning to post that to HN for a few weeks now, tbh.
- dev_0 4y agoSounds interesting.....but seems like the knowledge for this domain is exotic...
- shakezula 4y agoIt may sound it but I promise it’s not. Order filling is surprisingly simple but the devil is in the details, as always. https://dylanlott.com/orderbook https://dylanlott.com/orderbook If you’re interested in reading more. I’m planning a part 2 update to it soon. Edited to fix my link.
- robertlagrant 4y agoFYI your www link has a cert mismatch. Removing that fixes it.