1. Back to Basics
A helpful primer on asynchronous coding in JavaScript. This post covers callbacks, promises, and async-await.
Article No Longer Available
2. From 7.5GB to 32KB
An exploration on reducing memory allocation - starting from easy wins to more complicated optimizations.
3. Browser support or not, here I come
A list of new CSS units that are going to be specified in the upcoming CSS values and units module level 4.
4. The.Whiteboard.Interview
A retrospective on the whiteboard interview that cost a job. This post includes the question asked in the interview, how the author answered it then, and how the author would answer it now.
5. Sounds simple, right?
How would you answer this common interview question? Write a function that prints all the odd numbers up to 20.
6. Get up there!
This post is all about how developers can benefit from giving talks and presentations.
7. Sixth Sense?!
Synesthetes can taste sounds, smell colors or see scents, and research proves these people experience reality differently.
A community sourced response to experiences with programming synesthesia.
Article No Longer Available
That's it for our weekly wrap up! Keep an eye on dev.to this week for daily content and discussions...and if you miss anything, we'll be sure to recap it next Monday!
Oldest comments (3)
Look ma, I'm famous!
😄
Hi, Jess! Since this is a series you post often, felt like I should point out where some UI consideration would be valuable :)
I was skimming the list to see which ones I'd want to read, and then I got really confused about whether the article links were the beginning of the next section or the conclusion of the previous section. Here's where I was at the time:
I think it's because the section headers are the same size as the article titles, the whitespace doesn't distinguish where the boundaries are, and there were several in a row where the header and the article title weren't obviously related so I looked at the descriptions to see which they went with. But, eg the bottom description, "How would you answer this common interview question?" sounds like it belongs with "How to lose a job in 10 minutes", but it actually belongs with the other one. So that was like 3 or 4 ways I tried to look for hints on how to parse and wound up failing.
Not sure the best way to improve it, but figure my responsibility is just to point it out.
Anyway, cheers, and thanks for curating the articles :)
Ah, thanks for the note Josh! This post format can certainly use some fresh eyes.