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.

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.

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

https://en.wikipedia.org/wiki/American_Airlines_Flight_587

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.

"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"

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?

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.

My immediate advice to you as an engineer is to remember that your most powerful and valuable tool is your mind. The ability to solve software engineering problems starts with the cognitive aspects of your knowledge, intuition, experience and who you are. An engineer's cognitive ability to solve problems and guide outcomes is the most valuable thing that we bring to any project we join or undertake.

Look for a team or project that values critical thinking to drive execution over just banging out code. Don't sweat being hands on in the long run, i.e. writing code and pushing features. Make the most of the work you're doing now to start honing your skills to be able to drive things like architecture, implementation choices, etc. based on experience, lessons learned, people you enjoy working with etc.

Also, keep in mind that you have a unique albeit unfortunate set of circumstances that can bring a perspective as you're going through this to what works and doesn't for others in similar circumstances that want to have careers in software technology. Be open to an awareness for areas where you can help solve problems and be involved in building solutions for others in a similar circumstance as you're in. Look for ways to develop products, tools, advisory groups, training, etc. that can help engineers with similar disabilities.

I wish you the best and again, I'm very sorry you're facing this. I hope that my thoughts help in some way.

With the post a resume feature it's not clear how that data is being used to connect me to "the right recruiters" and makes me wonder if this is just a way for your service to collect and sell my resume and others to recruiters as data vs. matching resume content to the jobs directly then notifying me.

Also, if you have other sources for jobs besides LinkedIn, native or otherwise, I'd trust this service more if the links/listings had a LinkedIn (or wherever) label or icon to let me know the source before clicking through to the details.

Other than the concerns about LinkedIn as your only source of content and how your service is using my resume data, I think the site itself is easy to use, understand and ultimately could be a useful tool in finding remote work.

Comments URL: https://news.ycombinator.com/item?id=22659281

Points: 1

# Comments: 0

- Neil Peart, The Garden

Comments URL: https://news.ycombinator.com/item?id=21958796

Points: 2

# Comments: 0