Models | Examples |
---|---|
Display ads | Yahoo! |
Search ads |
- The Comprehensive Guide to Speaking at Technology Conferences in 2020 (https://www.cfpland.com/guides/speaking/)
- What I've learned after sending 147 proposals to 36 conferences in a year (https://drobinin.com/posts/what-ive-learned-after-sending-147-proposals-to-36-conferences-in-a-year/)
- Introduction to slides, a Clean Presentation Tool (https://zge.us.to/slides.html)
- A command-line based markdown presentation tool (https://github.com/visit1985/mdp)
- Giving a presentation with perfect UI/UX design (https://habr.com/en/post/471624/)
- Why Your Excellent Conference Talk Was Rejected (https://www.promptworks.com/blog/why-your-excellent-talk-was-rejected)
- Very Important Strangers (http://randsinrepose.com/archives/very-important-strangers/)
- Tips for Public Speaking (http://speaking.io)
- Presentation Skills Considered Harmful (http://seriouspony.com/blog/2013/10/4/presentation-skills-considered-harmful)
- Passionate Programmer: How to Give a Keynote (https://web.archive.org/web/20150211231805/http:/
Attention: the list was moved to
https://github.com/dypsilon/frontend-dev-bookmarks
This page is not maintained anymore, please update your bookmarks.
A lot of these are outright stolen from Edward O'Campo-Gooding's list of questions. I really like his list.
I'm having some trouble paring this down to a manageable list of questions -- I realistically want to know all of these things before starting to work at a company, but it's a lot to ask all at once. My current game plan is to pick 6 before an interview and ask those.
I'd love comments and suggestions about any of these.
I've found questions like "do you have smart people? Can I learn a lot at your company?" to be basically totally useless -- everybody will say "yeah, definitely!" and it's hard to learn anything from them. So I'm trying to make all of these questions pretty concrete -- if a team doesn't have an issue tracker, they don't have an issue tracker.
I'm also mostly not asking about principles, but the way things are -- not "do you think code review is important?", but "Does all code get reviewed?".
-
Download a Kindle-compatible version of the dictionary here. Unzip the .rar archive.
-
Get the "Send to Kindle" program on your computer. Here's the link for the Mac.
-
Right-click your recently downloaded (unzipped) dictionary file, and click the "Send to Kindle" menu item. It will arrive on your Kindle shortly.
-
Once the dictionary has arrived, go to your settings -- on my newish paperwhite, it's at Home > Settings > Device Options > Language and Dictionaries > Dictionaries > English. Choose the Webster's 1913.
(by @andrestaltz)
If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.
Picking the right architecture = Picking the right battles + Managing trade-offs
- Clarify and agree on the scope of the system
- User cases (description of sequences of events that, taken together, lead to a system doing something useful)
- Who is going to use it?
- How are they going to use it?
FWIW: I (@rondy) am not the creator of the content shared here, which is an excerpt from Edmond Lau's book. I simply copied and pasted it from another location and saved it as a personal note, before it gained popularity on news.ycombinator.com. Unfortunately, I cannot recall the exact origin of the original source, nor was I able to find the author's name, so I am can't provide the appropriate credits.
- By Edmond Lau
- Highly Recommended 👍
- http://www.theeffectiveengineer.com/
Answer: All APIs of Node.js library are aynchronous that is non-blocking. It essentially means a Node.js based server never waits for a API to return data. Server moves to next API after calling it and a notification mechanism of Events of Node.js helps server to get response from the previous API call.
Source: tutorialspoint.com