ryanmillerdev's profile picture. Sapere aude. Software engineer at Ediphi.

Ryan Miller

@ryanmillerdev

Sapere aude. Software engineer at Ediphi.

Ryan Miller reposted

Ten months ago, we launched the Vesuvius Challenge to solve the ancient problem of the Herculaneum Papyri, a library of scrolls that were flash-fried by the eruption of Mount Vesuvius in 79 AD. Today we are overjoyed to announce that our crazy project has succeeded. After 2000

natfriedman's tweet image. Ten months ago, we launched the Vesuvius Challenge to solve the ancient problem of the Herculaneum Papyri, a library of scrolls that were flash-fried by the eruption of Mount Vesuvius in 79 AD.

Today we are overjoyed to announce that our crazy project has succeeded. After 2000

I’ve heard it said that software engineering is inherently more complex than other engineering disciplines. Perhaps a better way to state this is that software can accrue complexity faster than any other medium. Easier to build a logical Rube Goldberg machine than a physical one.


What’s a term that describes the incredible ability some people have to comprehensively map a product/feature/topic in their head? It’s not raw knowledge, it’s the ability to speed run the conceptual graph, plot intersections, and detect places where ambiguity might remain.


When reviewing a pull request, do you solely review the code or do you try to exercise the new functionality as well? I’m surprised how rarely I see the latter. Especially when building something like a UI, can be hard to understand code without seeing it in action.


I’d love to know if this predication was right, esp. given Sp02 feature will accompany the Series 6.

I wonder if the new Breathe app for watchOS 3 is Apple's way of training the watch's pulse oximeter for Sp02 readings.



For anyone living in the Sumner / Bonney Lake area, made this list of profiles with info about Sumner Grade Fire.


A hard reality I've had to come to terms with recently is that, compared to @DuckDuckGo, Google search is magnitudes better at finding the perfect Stack Overflow answer for a given question. But still love @DuckDuckGo for just about every other purpose.


Looking back at the beginning of my developer career, I often conflated "writing software" with "solving the problem". The former is simply a means to the latter. It makes my day when I or a member of my team finds a simpler way to do something that doesn't involve code at all!


Ryan Miller reposted

v1.0.0 released! deno.land/v1


A rule that’s served me well: write the bare minimum amount of software to solve a problem completely. Anything past that is a liability.


If you (or someone you know) could benefit from some pro bono web development help, I'm making myself available: calendly.com/andryanmiller/…. I can't sew masks, but I can fix websites, and want to help as I'm able!


Used to think HTTP range requests were limited to bytes, which is a sensible use case but nothing I'd encountered in the wild. Turns out you're free to use any range unit you wish (see RFC 7233#2.2). Here's a basic pagination example:

ryanmillerdev's tweet image. Used to think HTTP range requests were limited to bytes, which is a sensible use case but nothing I'd encountered in the wild. Turns out you're free to use any range unit you wish (see RFC 7233#2.2). Here's a basic pagination example:

How staggering it is that the web evolved from this rather casual proposal to what is arguably a human right in only thirty years: w3.org/History/1989/p…


Idea: capability tiers for browsers. Grade 1=HTML,CSS, Grade 2=JS, Grade 3=Web APIs, Grade 4=⁉️. If we assume every new browser entrant needs to hit the highest tier, as we currently do (and why Chromium is entrenched), we're going to keep playing into Google's hand.


Useless HTTP trivia: trailing slashes are appended to every request to a root domain. See tools.ietf.org/html/rfc2616#s…. We're accustomed to using URLs like example.org, but they're technically malformed. Browsers help us out behind the scenes.


I always thought data-* attributes were a loose convention on the web, perhaps aiming to increase readability. Not so! It's actually baked into the HTML5 spec: html.spec.whatwg.org/dev/dom.html#e…. In fact, elements possess the dataset property, which can be used like so:

ryanmillerdev's tweet image. I always thought data-* attributes were a loose convention on the web, perhaps aiming to increase readability. Not so! It's actually baked into the HTML5 spec: html.spec.whatwg.org/dev/dom.html#e…. In fact, elements possess the dataset property, which can be used like so:

What's the smallest (valid) HTML document one could write? Throw out <html>, <body>, and <head>: only Doctype and <title> are necessary (per validator.w3.org and google.github.io/styleguide/htm…). File that in questions I thought I knew the answer to...

ryanmillerdev's tweet image. What&apos;s the smallest (valid) HTML document one could write? Throw out &amp;lt;html&amp;gt;, &amp;lt;body&amp;gt;, and &amp;lt;head&amp;gt;: only Doctype and &amp;lt;title&amp;gt; are necessary (per validator.w3.org and google.github.io/styleguide/htm…). File that in questions I thought I knew the answer to...

Ryan Miller reposted

Hidden gem: a 49 page history of HTTP cookies on @arxiv: arxiv.org/abs/cs/0105018. Intricately retells how @montulli and David Kristol brought the spec to life and how 🍪’s eventually became the privacy flashpoint we now know today.


Loading...

Something went wrong.


Something went wrong.