wmij

Thanks for sharing this. I grew up a few miles away from the Sikorsky plant in Stratford, CT. and as a kid remember seeing on a couple of occasions some of the experimental helicopters flying overhead. A lot of my friends parents worked at Sikorsky and sometimes would mention the program, in particular the ABC (advanced blade concept). It was mainly hushed but after what seemed like many years the experimental programs were moved out of Stratford or maybe scrapped. Then all the overhead traffic everyday were from the Blackhawk and Super Stallion programs the company was focused on to keep themselves going.

I still marvel at the Sikorsky Skycrane, IMO one of the most underrated aircraft ever produced. Whenever I see one I'm transported back in time seeing them flying over my neighborhood thinking that it was like a big giant wasp in the sky.

Yes. The ability to turn features on and off, especially on demand is an important part of the applications and services my team is responsible for. We have a few different levels where features can be enabled or disabled ranging from configuration injected into applications, configuration stores to lookup settings giving us the ability to expose/hide features.

To support per user or group settings we have a `canary` role that can be set to allow access to new features that have been integrated but not available to the general users. The nice thing about having something tied to roles is that the changes can take effect immediately without the need for redeploying, or reinitializing applications in our footprint. Also, the role based model can be made as fine or coarse grained suited to the app's and user's being served.

We tend to avoid encoding feature flags into URLs because users can bookmark them, revisit via history or navigate from old emails, messages, etc. and we'd rather not expose these flags or have them memorialized anywhere.

This just recently happened to me with an old eBay account I've had 20+ years. After reading the story in the document above, you could easily search/replace Apple for eBay and it's identical to my story, aside from emailing the CEO. The reason given in the permanent suspension message to me was a vague reference to the TOC docs and links to support that all lead to dead ends. After, resigning myself to not caring further, because I use eBay these days rarely, the next day my account was just as suddenly and without reason reinstated, as if nothing ever happened.

I'm left scratching my head as to what the reason(s) were for this to have happened and can only think of 3 possibilities.

- An overzealous, newbie type operator that suspended me by mistake - Some kind of error in automated flagging and error in review - eBay's radical way of engaging with me to spur me to buy/sell again as the account's last activity was more than 1 year ago

It is the "chief" type roles in a company - CEO, CTO, CFO, COO, CMO, etc.

I knew about the story of Phil Katz having read this article before and was also a user back in the day, but just recently watched the movie 'Leaving Las Vegas'. Reading the PK article again in the link reminded me so much about the movie. If you haven't seen the movie it's worth watching and maybe an insight into the problems he was going through.

Maybe, I'm being somewhat superficial but I can't help to wonder that the name of the company/app "Quibi" only hurt their launch and not helped aside from other factors pointed out.

I wonder how many times in talking about the app have people needed to spell it out or say it's pronounced like "kwibee" not "keebee", etc. I actually needed to go to wikipedia.org to see the exact pronunciation.

So much about the branding reminds me of the "Cuil" search engine failure a decade ago. I remember seeing the original name "Cuill" in some of my request logs and thinking at the time that it was some malicious DDOS bot that wanted to see my site as "see you ill". First time that I saw in the news about "Quibi" I immediately thought of the whole "Cuil" search engine failure. Not a great first impression, but that it was.

One aspect of Eddie's playing that rarely gets mentioned was his rhythm and chord playing. His chordal phrasings and how he could make a song sound huge for just a single guitarist was amazing. AND The first few early albums were mixed with the main guitar track panned hard left.

One of my favorites from his Edna character.

"Edna: Which of the following would you most prefer? A puppy, a pretty flower from your sweetie, or a large, properly formatted datafile?

Scammer: I would choose the datafile"

I'm also in the GitHub as a tool vs. social app camp and have rarely if ever had the inclination to visit the daily trending page (cue Pete Davidson - "my bad"). One feature I do like though is to see what repositories get starred by people I follow.

One thing has left me wondering after reading the article, is what the algorithm has changed to if it used to be just most stars in the given time period? Does anyone have any insight in how the trending repos are ranked?

For example from the article:

> ... the notion that stripe-samples/subscriptions-use-cases, which has 13 total stars with exactly zero new stars today is the new JavaScript “hotness” is a joke.

I'm left wondering then how did that get to the top? Views? Clones? API requests? Something else like paid promotion? Or manual curation?

Looks great man. Once you have your main board set (like you do), don't forget to think outside the board you've built to add things like a wah and volume pedal. For me these have both been staples of my rig that sit outside the "effects" part and can be be added/subtracted as necessary.

> Don't write unit tests. Don't accept pull requests. Simply write software for yourself and have fun doing it.

There's a careful balance here though right? For most projects your first users or clients are the unit tests. Why not have a future of repeatable client/user tests that insulate from regressions and to be your wingman to navigate future iterations? Also for me, I still review and accept my own pull requests on solo projects, because it is that last step when working on my own where I know I'm at a good point looking at my diffs and the last step in introducing mistakes.