or subscribe with
Join 14,100+ readers for one email each week.
Digests » 219
Barcelona, 4-8 Sept. 2017 – Are you a curious mind? Full Sack Fest is a week-long conference based in the amazing city of Barcelona that peeks into the web of tomorrow. Serverless, Blockchain, WebVR, Distributed Web, Progressive Web Apps... Come and see! Early bird tickets available with a 10% discount using the code DIGEST.
this week's favorite
Similar to the images on allrgb.com, make images where each pixel is a unique color (no color is used twice and no color is missing). Give a program that generates such an image, along with a screenshot or file of the output (upload as PNG).
Earlier this year, our CEO, Steve, mentioned we are redesigning the site. Great! But how? Frontend engineering is in a very different state than it was when Reddit was first conceived. We have a large depth of options for just about every layer of web app development. From how to render views, style content, serve assets, and write code, frontend development has at least a couple of options. One of the first questions we had to answer was “what language should we use?”
The VM has a memory area of 100 cells, indexed as 0-99. Each cell can contain an instruction or an integer value. There's also a stack, which starts at the bottom of the memory area and grows upward.
You should hire an old programmer. It’s true! Sure.. older programmers are not going to work as many hours as someone fresh out of college. They have kids and spouses and mortgages and softball games to attend. They won't hang out at the office playing Xbox and ping-pong all night. They will not work 80 hour weeks and they will actually use their vacation time. And of course they cost more than young programmers.
Instructors of "Introduction to programming" courses know that students are willing to blame the failures of their programs on anything. Sorting routine discards half of the data? "That might be a Windows virus!" Binary search always fails? "The Java compiler is acting funny today!" More experienced programmers know very well that the bug is generally in their code: occasionally in third-party libraries; very rarely in system libraries; exceedingly rarely in the compiler; and never in the processor.