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
Wake turbulence was a factor in the crash of AA587 from JFK back in 2001. The FO flying the take off encountered wake turbulence from a 747 that took off just prior and overused the rudder in response to the point it snapped the tail of the jet, an A300.
Oddly a similar engine incident happened on the same United flight route back in 2016. Apparently it was a bird strike back then. Link: http://avherald.com/h?article=4999bec5
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.
Ok, thanks. I set what I thought was a username during signup but looks like that was just the name. I see now there's a second step going to https://spacehey.com/settings and the username URL is working for me.
The original myspace used the profile name for URLs - https://myspace.com/some_name - maybe the reboot will eventually. I tried with mine and it was a 404.
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.
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.
First off, I'm so sorry to hear that you've been diagnosed with this condition. I haven't read through any of the replies to your question aside from a quick read through, so I'm sorry if any of my advice is redundant, helpful or not.
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.
Are there other sources you're using besides LinkedIn? I ask because every job listing I clicked on is taking me to LinkedIn as the next step to learn more details and apply. I realize that you're probably just getting this off the ground and leveraging LinkedIn's data, but I'd trust and recommend a service like this where there are native listings and not just an aggregated wrapper over LinkedIn. Why not just use LinkedIn to begin with?
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.
Yes, absolutely, every day. Revision history really is a critical part of the development and code review process. My team uses Git/GitHub and for me using diffs across previous commits and the blame representation especially for files in large pull requests gives me a tool to understand the changes better when reviewing changes on older files.
A lot of times when a developer is working on a larger change that could be adding/expanding a feature or doing some larger refactoring, they may fix or improve something loosely related to the primary changes. If the unrelated changes don't have a separate commit I will request a dedicated commit be kept to document and have separate history so we don't lose the context in the larger body of work when squashing prior to merge.
Tagging releases is another tool for tracking revision history across releases that has come in handy for diffing and viewing the state of the code more holistically than looking at files in incremental commits or individual blames.
"The treasure of a life is a measure of love and respect
The way you live, the gifts that you give
In the fullness of time
It's the only return that you expect".
Something that has helped me with recognizing incremental progress on long running side and personal projects where completion seems so far off is relating it to the crawler vehicles NASA used to get the Space Shuttle to the launch pad.
Incremental progress and speed seem slow (1 mph), but eventually you will get into position for launch.
This has helped me understand how weight and physical constraints (these == time commitments to a primary project, family, sleep, etc.) impact velocity on where you start from getting to an eventual goal (starting a side project and coming to release, launch, etc.). Some things just can't travel faster than 1 mph due to external constraints.
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.