Every Monday we round up some of the last week's top posts, comments, and tweets. If you have any feedback, please leave a comment. â¤ï¸
Imminent deadlines make devs cut corners. Just ask our company's furry mascot:
The Practical DevThe last programming book you'll ever need18:42 PM - 04 Mar 2016
So Aga Zaboklicka reminds us to remain focused on quality even when there's a lot of time pressure on your project, since otherwise you'll be dealing with technical debt well into the future:
As most of us know, code is usually not in its best form the first time we write it. That's why we have to change it sometimes. Or refactor itâ€”what's the difference anyway? Jason McCreary clues us in:
Commenters weighed in on the value of short but inaccessible code, which is often not very helpful:
I couldn't agree more about one-liners. Also using "tricks", little-known features and other "clever" stuff usually just makes the code harder to comprehend. IMHO the code example above doesn't really need refactoring anyway.
When Kathryn Grayson Nanz was a kid, her dad let her blame stuff on him if she ever felt uncomfortable doing something. She relates the experience to modern workplaces, where there's often a routine scapegoat for every scenario:
Computer vision is just about the coolest game in town these days. If your machine can't recognize what is a hot dog and what isn't, why even get out of bed in the morning?
Anyway, Jordan Osterberg played around with Apple's new augmented reality platform, ARKit, and figured out how to identify objects seen in his computer's camera.
Last week one of our top posts explained HTTP. Well it turns out that there's more than one protocol aroundâ€”indeed AMQP (Advanced Message Queuing Protocol) is a popular choice for message-oriented middleware.
Federico SÃ¶renson runs down the differences:
It's easy to make a GIF about microservices:
The Practical DevMicroservice architecture visualized14:45 PM - 24 Mar 2017
It's a little more involved to actually understand how they work and when to implement them. Thankfully, Aditi Chaudhry has us covered:
Chris Dodds, a DevOps specialist, says that early in his career he would define his job mostly in terms of automation. But now he realizes that automation really only describes a small portion of his job:
That's it for our weekly wrapup! 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!