Matt Steele

The neverending side project

Matt Steele, ruminating on the side project that he's been hacking on since 2011: A long-lived side project gives you the chance to confront your old habits and see how far you've progressed. Over the years, he's rewritten the Super Bowl Squares app 5 different times. One of his findings: A long-lived side project also gives you breathing room to ask how much stock to put into trends. My original jQuery app still loads faster, has 60% less code, and (to my mind) is more understandable than my latest version built atop Angular 5. Have I actually made things better? Have we as an industry? Good question!

logged by @jerodsanto 2018-02-13T17:01:00.009558Z permalink #practices

HelloFresh Icon HelloFresh – Sponsored

Learnings on designing your first microservice

If you're in the beginning of your journey to build and deploy your first microservice, read this post from our friends at HelloFresh. Don’t reinvent the wheel, unless it’s extremely necessary or you have all of the time and resources in the world. This is one of the easiest mistakes to make. We did it with the conviction that this would benefit us enormously down the road, and, 6 months later, we realized how wrong we were. Here's what we learned... HelloFresh is hiring ~> Senior Backend Engineer in Berlin

logged by @logbot permalink

Indie Hackers Icon Indie Hackers

Am I too old to do a coding bootcamp?

Imposter syndrome is alive and well. It's up to us, the community, to fight back against the voice inside our heads telling us we don't belong, or we can't do it. Here are some of my favorite responses... Never too old. Do it! I'm 60 years old and just launched my own venture... You don't have to "fit into the tech scene" to be a developer. I was 33 when I went through a coding boot camp after almost 16 years of being a fire fighter...that was 4 years ago. I'm currently in a coding bootcamp and I'm 36 years old. I'm 71 and I program every day. You are !imposter

logged by @adamstac 2018-02-12T21:43:08.665067Z permalink #learn

CockroachDB Icon

Your database should work like a CDN

What do you use when your app needs to provide speed and availability to a global audience? You need a distributed database that... Deploys anywhere Reduces latency by performing reads and writes close to users (while still enforcing consistency, even across a distributed deployment) Maintains uptime by tolerating faults Offers granular control over geographical placement of your data for GDPR compliance Sounds like a CDN.

logged by @adamstac 2018-02-12T20:42:00.009094Z permalink #cockroachdb #database

Chrome Icon

Netflix 1080p

Turns out Netflix enforces its video stream to only be played in 1080p on ChromeOS devices. And it does it by... client-side JavaScript detecting the user-agent! 🤦‍♂️🤦‍♀️ This Chrome extension undoes that for you.

logged by @jerodsanto 2018-02-12T17:31:00.008663Z permalink #chrome

JavaScript Icon

Front End Interview Handbook

Remember the Front-end Job Interview Questions project that we talked to Darcy Clark about way back in the day? Well, this is the answer to that project. Literally. It's answers to the questions. It dubs itself as: almost complete answers to "Front-end Job Interview Questions" which you can use to interview potential candidates, test yourself, or completely ignore They forgot to mention the other use case: memorizing the answers just in case your interviewer pulls questions directly from this list 😉

logged by @jerodsanto 2018-02-12T16:24:00.009533Z permalink #front-end #javascript

Command Line Heroes Icon Command Line Heroes – Sponsored

DevOps_Tear Down That Wall

For the longest time, there was a wall dividing developers and operations. Find out what it took to tear that wall down and embrace DevOps as a cultural practice. This episode explores why that matters for the command line heroes of tomorrow. — Episode 4: DevOps_Tear Down That Wall Command Line Heroes, a new podcast from Red Hat, takes you on a journey of epic true tales of the developers, hackers, and open source rebels revolutionizing the tech landscape. Subscribe wherever you get your podcasts or head to to learn more.

logged by @logbot permalink

Thoughtbot Icon Thoughtbot

The mechanics of Maybe

Joël Quenneville: Our world is full of uncertainty. This uncertainty bleeds into our programs. A common way of dealing with this is null/nil. Unfortunately, this leads to even more uncertainty because this design means any value in our system could be null unless we’ve explicitly checked it’s presence. Imagine how many developer-hours are wasted globally each year dealing with null/nil. The number would probably astound us. The major advantage of guard clauses is to suss out invalid inputs (often nils) at the perimeter of your program/module/function, so the rest of your code doesn't have to concern itself with these uncertainties. But Maybe there's another way... In Elm, all values are guaranteed to be present except for those wrapped in a Maybe. This is a critical distinction. You can now be confident in most of your code and the compiler will force you to make presence-checks in places where values are optional. Click through to learn the mechanics of it all.

logged by @jerodsanto 2018-02-12T15:23:00.040804Z permalink #fp #elm

CSS Icon

Everything easy is hard again

This is a long, nuanced piece about progress in web-building technologies and practices. It's written from a designer's perspective, but many of the themes ring true to my developer's brain. I wonder if I have twenty years of experience making websites, or if it is really five years of experience, repeated four times. If you’ve been working in the technology industry a while, please tell me this sounds familiar to you. The primary example cited is how we answer the simple question, "How do I put two things next to each other?" The status quo has changed (tables -> floats -> Flexbox -> CSS grids), but to what advantage? A few of his points feel a bit like looking back at the "good 'ole days" through rose colored glasses, but his case is mostly well-reasoned and powerful. the foundations are now sufficiently complicated enough on their own that it seems foolish to go add more optional complexity on top of it. I’ve kept my examples to the most basic of web implementations, and I haven’t touched on Javascript, animation, libraries, frameworks, pre-processors, package managers, automation, testing, or deployment. Whew. Whew, indeed! The breadth and depth of knowledge required to feel competent in today's web ecosystem is probably why we spend so much time dealing with imposter syndrome in this industry.

logged by @jerodsanto 2018-02-12T14:19:00.08510Z permalink #design #css #practices

Rico Sta. Cruz Avatar The Changelog #283

Devhints - TL;DR for Developer Documentation

Rico Sta. Cruz joined us to talk about his project Devhints — cheatsheets for developers! There are more than 365 cheatsheets you can contribute to and it's open source. We talked about the design, technical implementation, community, and alternate interfaces (CLI). We also covered RSJS, RSCSS, and Docpress. You have to sell what it is you're building in your documentation. It's not just describing what it is and how to use it. It's about telling interesting stories. — Rico Sta. Cruz

logged by @adamstac 2018-02-09T23:18:08.927265Z permalink #practices #javascript #css


A decentralized StatusPage with no single point of failure published to IPFS

There are only two things required to make a status page good: availability and accuracy. It turns out you can get the first thing for free by publishing it to the permanent web! Slowly, surely we are seeing more and more excellent use cases for IPFS. We've been keen on this tech ever since we did a show about it with Juan Benet a couple years ago. It's worth a re-listen.

logged by @jerodsanto 2018-02-09T16:49:00.010299Z permalink #ipfs

WebKit Blog Icon WebKit Blog

PWAs on Safari?!

Workers will be at your service in an upcoming release of Safari — specifically Safari Technology Preview 48, macOS High Sierra 10.13.4 and iOS 11.3 beta seed 2. Youenn Fablet, software engineer at Apple, writes: While WebKit’s implementation and feature set is quickly evolving, we believe it has reached an important milestone in terms of functionality and compliance: applications using service workers for offline support or network/cache optimizations run successfully on latest WebKit builds. Let’s now dive into the specifics... There are threads on Twitter here and here you should check out for commentary on this spec. This news comes after Microsoft announces PWAs are coming to Microsoft Edge and Windows.

logged by @adamstac 2018-02-08T18:14:41.016416Z permalink #webkit #safari #pwa Icon

This is how I coined the term "open source"

Corroborated here and here (kinda). This quote from Christine Peterson is like a mic drop. The introduction of the term "open source software" was a deliberate effort to make this field of endeavor more understandable to newcomers and to business, which was viewed as necessary to its spread to a broader community of users. The problem with the main earlier label, "free software," was not its political connotations, but that—to newcomers—its seeming focus on price is distracting. A term was needed that focuses on the key issue of source code and that does not immediately confuse those new to the concept. The first term that came along at the right time and fulfilled these requirements was rapidly adopted: open source. Thank you Christine for sharing this much needed history of how we got here.

logged by @adamstac 2018-02-08T17:33:00.008881Z permalink

Ping! Icon Ping!


A sharded First-in First-out queue using Redis and Resque. This gem unables you to guarantee in-order job processing based on a shard key. Useful for business requirements that are race-condition prone or needs something processed in a streaming manner (jobs that require preservation of chronological order).

logged by @jerodsanto 2018-02-08T16:32:00.013015Z permalink #ruby #redis

iOS Icon

Someone published the source code to iBoot (a critical piece of iOS) on GitHub

This is being called "the biggest leak in history", which is probably not true (remember when Gizmodo got its grubby paws on the iPhone 4?). But it's likely the biggest leak in Apple software history. Motherboard says it... could pave the way for hackers and security researchers to find vulnerabilities in iOS and make iPhone jailbreaks easier to achieve. That's plausible. iBoot is responsible for ensuring a trusted boot of the O/S. The specific version posted was from iOS 9, but this portion of code probably doesn't get updated as often as the Music app, so it's likely still relevant. Apple promptly posted a DMCA takedown request, and the source code is no longer publicly available. But we developers know all to well that once source code is made public, there's no taking it private again.

logged by @jerodsanto 2018-02-08T14:39:54.81557Z permalink #ios #security
0:00 / 0:00