/explore
|
You are here 
|
truemped.github.io | ||
| | | | |
blog.kemonine.info
|
|
| | | | | It would seem I've regained the ability to write more frequently and regularly despite my health hassles My Preference Normally I write posts for this blog by hand using a pen, Tomoe River paper and a clipboard. Sadly, my health hassles make this approach to writing very difficult and I do not have the capacity to write using analog methods regularly or reliably. Over the last few years I've had to patiently wait for windows when my health hassles doesn't interfere with my writing. With analog I have to slowly write blog posts over the course of weeks and sometimes months. It's quite frustrating but I enjoy writing and refuse to give it up, even if frustrated by my health hassles. | |
| | | | |
markodenic.com
|
|
| | | | | Free programming books, algorithms, public APIs, and much more. | |
| | | | |
aaronbos.dev
|
|
| | | | | Podcasts have become very popular over the years and you can almost guarantee that there is a podcast available for any of your personal interests. In this post, I'll describe how I believe podcasts have helped me grow as a developer. We'll also take a look at some of my favorite podcasts and discuss a little bit of what they're about and why I enjoy them so much. | |
| | | | |
www.hillelwayne.com
|
|
| | | Caveats: I'm not an interviewer, I've never done serious research on interviews, and I haven't tested this. I propose this entirely as a thought experiment. Assumptions: We interview at jobs to find ideal candidates. WE are looking for candidates who are Good at programming Good at software engineering Can work in a team A "culture fit" (not an asshole). Technical interviews test the first two. They are primarily whiteboard questions, abstract design questions, or "write this program" questions. | ||
