It requires us to sign up to try it. Can you share a demo video or allow us to try it without signing up?
217 karma · joined April 23, 2021
On institution benefited from the lion's share of this: University of Limerick. I recall the then-President of the university saying in an interview that he was under extreme pressure to reveal the source of investment as there was a significant drug problem in the city at the time and people were speculating it was the proceeds of crime! Another story that came out years after the fact was that he once invested millions in third level education in Ireland on the condition that the government match it, which they reluctantly did.
1: 112 call to an ambulance
2: Ambulance arrives, takes an ECG and gives aspirin and GTN
3: Paramedics drive to the emergency department
4: ER doctor identifies the patient is having a heart attack, and pages cardio
5: Cardio decide the patient needs a stent and they bring them to an OR to have it fitted.
In each of these steps, the patient could go into cardiac arrest and likely will not survive.
Today it looks more like this:
1: 112 call happens, the call taker follows a protocol that asks the caller to administer aspirin if appropriate while the ambulance is on the way
2: Ambulance arrives, takes an ECG, identifies a heart attack and transmits the ECG to a cardiologist, all while treating the patient
3: Cardiologist thinks the patient would benefit from a stent, so the paramedic begins transporting the patient and administers whatever pre-operation drugs the cardiologist wants (this would normally happen at step 5 in the previous example)
4: Patient is brought direct to the OR (or PPCI as they're specifically called here) where the cardiac team are waiting around the table for the patient
It's so efficient. I'm not up to date with the latest research on this but just the time savings alone must have saved so many lives. Treatment starts far sooner and all unnecessary steps are removed.
- We have a team that can assess submissions now to save companies time.
- We published our assessment rubrics for each test so companies can use this to save time, if they wish to assess submissions on their own.
- We've added a whole lot of new tests. Some can be done in any language, some are more specific (rust, react, C#, Java, etc.).
- Add an activity log to give reviewers an insight into the timeline a candidate followed for their interview.
One part of this that we've yet to truly crack is pricing; in the background we're offering various different pricing models that each work well for certain companies but haven't found a one-size fits all yet.
At the early stages when you're defining your strategy? "Good strategy/bad strategy" by Richard P. Rumelt. "Strategy" is thrown around a whole lot in business, often by somebody who is talking about a goal, as opposed to how to reach it. This book can get a little repetitive but the overarching teachings are valuable and will serve you well throughout your entrepreneurship journey.
After the startup phase (growth/acquisition)? I recommend "The messy middle" by Scott Belsky.
Intercom cofounder Des Traynor's announcement: https://twitter.com/destraynor/status/1635705915595685902
Also - kudos for open sourcing it. I look forward to contributing and using the library.
0: https://devscreen.io/inclusive-language-check 1: https://github.com/retextjs/retext-equality/blob/main/rules.... 2: https://github.com/retextjs/retext-profanities/blob/main/rul...
Edit: I have just noticed that this hasn't had any commits in 3 years, and no releases for much longer than that. OP: are you the author of the library? It would be good to hear what the plans are for it.
If I were in that situation I'd send a get well soon card and flowers. I wouldn't call or visit. Usually the only thing you have in common is work, so you're left to speak about either work or their heart attack. The latter is not really your business and the former is something they shouldn't be worrying about right now, so keeping these gestures one-way is a nice way to say "we're thinking of you and hope you get well soon" without the risk of putting them in an uncomfortable situation.
Good luck, and I hope they make a full recovery.
1: The aircraft entered into free-fall (i.e. falling at ~9.81m/s) at a low altitude and recovered within 1425ft. This would mean the wings were fully stalled and there was no drag or lift forces on the airframe while it was falling.
2: None of the many passengers on board felt the need to share it on social media.
Both of which are highly unlikely. I'd like to see the report of what actually happened, but I'm not sure if that will be forthcoming since it's a voluntary safety report. I'm not sure if they're treated similarly to NTSB investigations where the reports are made public.
The engineer-manager pendulum: https://charity.wtf/2017/05/11/the-engineer-manager-pendulum...
Questionable advice - is there a path back from CTO to engineer? https://charity.wtf/2022/07/29/questionable-advice-is-there-...
My main complaint is that their pricing is a little odd. Charging per developer doesn't work well for us when we sometimes have 5 devs working on the data vis and other times there are none.
I think your best options are to speak with your manager about it or start looking for other jobs with better work-life-balance. The companies you are looking for certainly do exist!
People can get so caught up in the numbers on a dashboard or AB test that they forget that there's a human on the other end that just got duped into a 4 figure expense. Gross indeed!
The Stanford course, for the curious: https://web.stanford.edu/class/cs9/
The product we're working on: https://devscreen.io
C# and .NET have been pretty easy to develop in, but the documentation was very poor I thought. Maybe I just didn't find it, but it lacked a good example walkthrough like you get with Rails. Next up is a Swift backend using Perfect[0]!
I'm not approaching it with any real goal other than to see how some other frameworks work but it feels very worthwhile.
We made the decision early on to aim for solutions that work well for both the candidate and the company, but where they conflict, go with what will work best for the candidate. This may seem counterintuitive from a business perspective, but it has served us well and, I think, it is the best way to go long term. Ultimately if we can give a great candidate experience then that's good for the business too.
Incidentally, I think the equally common advice of "solve a problem that you have yourself" is coming from the same place: you can't solve a problem without understanding your users.
I think the more general topic of brands taking political stances is worthy of debate, for sure. I tend to think it's fine. If I agree, great. If I don't, then I can choose spend my money at a company whose values align better with mine.
It sounds like you've had good financial habits during the good times and have a good chunk of money saved and invested. That's a great place to be. If you lost all of your income sources tomorrow, would it take you long to find another job? ANY job? There are still lots of tech jobs out there, but there is also an abundance of service work in many cities that they cannot fill. That could be enough to cover expenses, though you probably won't save.
Aside from the above, I would recommend seeing a therapist to help you navigate this time in your life.
Anecdotally, I see this a lot in organisations that have various operations teams (product ops, design ops, recruitment ops, etc.). It is often the responsibility of these teams to create processes and frameworks for other teams to work within. I think there's less willingness to push back against these teams when they want to introduce new processes than if, say, a single product manager(or designer, recruiter, etc.) proposed a new process.
I have two questions if you don't mind:
1: onboarding is something that users should do once only. Unfortunately, engineers only see it once also. It's easy to forget there's an onboarding flow in your app as you build it. Do you have mechanisms in place to detect if somebody releases a breaking change? For example: an element you expected to exist is now gone, a url has changed, etc.
2: Can you share how you came up with the problem and if the product evolved over your time in YC? I think most engineers or PM's have had to think about onboarding at some stage so I'm curious about that.