(Disclaimer: I work for shipyard.build so i am biased here..)
Dev-owned testing (or even dev-involved testing) is much more realistic when devs have shorter feedback loops between their code and its deployment. So often i've seen momentum get lost when devs have a wait period before they can run tests/do basic manual testing. Then the test aspect becomes the thing that "slows down" devs before they ship a feature, so they might tend towards shortcuts
Dev-led testing is too fundamentally different from a QA function, just as any amount of E2E tests can't replace manual testing. Each tries to solve for a different type of problem. Is it possible to do effective dev peer "QA" without essentially duplicating the QA role? And forget about testing one's own work..
DORA, recently, has been moving towards its own sphere outside of DevOps, hence why the acronym isn't usually expanded. So many of the core principles of DevOps (communication, collaboration, working across teams, etc) have impact beyond the DevOps discipline. DORA has been venturing into platform, DevEx, AI, etc.
From last year's DORA report:
"We are committed to the fundamental principles that have always been a part of the DevOps movement: culture, collaboration, automation, learning, and using technology to achieve business goals. Our community and research benefit from the perspectives of diverse roles, including people who might not associate with the "DevOps" label. You should expect to see the term "DevOps" moving out of the spotlight."
> Because ephemeral environments are reproducible on demand (via Docker images, Kubernetes pods, or a cloud VM), you can guarantee that each bisect step sees the same conditions. This drastically reduces "works on my machine" fiascos.
Agree on this pattern for all code changes. Hard to understate the amount of time we've saved by testing against the full prod-like environment right away. An ephemeral env implementation makes this easy and low stakes, so diving right into E2E testing a copy of your real infra isn't wildly unreasonable. However, I work for Shipyard (https://shipyard.build) so I'm a bit biased on these processes.
I'd be curious to know how the market is for frozen dinners designed to be microwaved on/in a separate plate/bowl. I usually do that anyway for things that come in plastic microwavable containers
Round rect technique aside (fascinating stuff!), the storytelling here is really charming. Reads like a clever short story
> Bill returned to Texaco Towers the following afternoon, with a big smile on his face. His demo was now drawing rectangles with beautifully rounded corners blisteringly fast, almost at the speed of plain rectangles.
I remember there being some buzz a few months back around something similar happening with Spotify. Lots of random tracks that looked/sounded suspiciously AI-generated strewn into Spotify-generated playlists.
My college's yield increased every year I was there, we got "the largest freshman class historically" four years in a row, even with their efforts to account for the new higher yield.
It's hard to accept the right number of applicants when yield isn't exactly linear year to year
AFAIK, my highschool still is offering BASIC in their intro CS curriculum. It's just so accessible and many of us preferred it over Python for intro classes
I always prefer the bottle filling stations over drinking fountains, for the 20% of the time that I actually have a bottle with me.
In gyms/libraries/airports it always feels like refilling stations get 5x more use than drinking fountains, but when you're anywhere else, what are the odds you're carrying a bottle?
When I lived in Boston, the thing that kept most of my friends from driving during weekdays was how profoundly aggressive the drivers tended to be. There are very few cities where I've seen that level of road rage
Exactly. Bug bounty seems like one of the smartest financial decisions a company can make. As for devs, it seems like a good deal if they're going to be finding these vulnerabilities anyway
> Still, I like the idea of using a browser from a company that does not want to access my data on their own servers.
Mozilla's motives alone for creating a web browser are why I trust FF. I don't like the idea of Chrome subsisting (to the point it's their actual business model) on my personal info
This. And in many cases, it was not just a supplement to their streaming catalogue. A family friend lives in Alaska and has a very low data cap and relied on Netflix's DVD service, and obviously can't be use Netflix anymore. I get cases like this are a very very low percentage of their userbase, but still unfortunate for so many to lose access to an easy media solution that never cost Netflix much to begin with
Dev-owned testing (or even dev-involved testing) is much more realistic when devs have shorter feedback loops between their code and its deployment. So often i've seen momentum get lost when devs have a wait period before they can run tests/do basic manual testing. Then the test aspect becomes the thing that "slows down" devs before they ship a feature, so they might tend towards shortcuts