ellard
Remote: Yes
Willing to relocate: No
Technologies: I'm flexible and willing to learn languages/frameworks based on the company's needs. My most recent stack was Ruby on Rails + React but i've also had professional experience with Python + Flask, PHP, etc.
Résumé/CV: https://docs.google.com/document/d/e/2PACX-1vQ7DMdxZx9dLYpng...
Email: [email protected]
I've been a software engineer for over a decade who's become more interested in the engineering leadership/mentorship side of the career. My last position was an Engineering Manager in Omada Health and I left that role in December, 2022 for personal reasons and to take some time off. I'm now refreshed and am raring to get back to building great services that improves peoples' lives.
I'm interested in Engineering Management positions. I have a preference towards the health and education sector, and prefer small to medium sized companies. If this lines up with what you're looking for or you want to learn more, shoot me an email and let's chat!
(I don't have an opinion on this; the closest I ever got to city planning was playing Sim City)
Omada Health is on a mission to inspire and engage people in lifelong health, one step at a time. We’re looking for Rails/React engineers to join our team and help build out our platform to support our members and to improve Omada's ability to reach out to more lives.
As a key member of our engineering team, you will help design, build and maintain systems necessary for rapid growth. Our team practices pair programming so you will have the opportunity to learn new techniques and share your skills.
Check out our press release here regarding the impact of personalized coaching to health outcomes: https://www.businesswire.com/news/home/20211026005385/en/Oma...
We can only hire folks who physically reside in the US.
Senior Software Engineer, Member Growth: https://boards.greenhouse.io/omadahealth/jobs/3552347
Senior Software Engineer, Full Stack: https://boards.greenhouse.io/omadahealth/jobs/3360101
Other open positions can be found in https://www.omadahealth.com/careers
Omada Health is on a mission to inspire and engage people in lifelong health, one step at a time. We’re looking for Rails/React engineers to join our team and help build out our platform to support our members and to improve Omada's ability to reach out to more lives.
As a key member of our engineering team, you will help design, build and maintain systems necessary for rapid growth. Our team practices pair programming so you will have the opportunity to learn new techniques and share your skills.
Check out our press release here regarding the impact of personalized coaching to health outcomes: https://www.businesswire.com/news/home/20211026005385/en/Oma...
We can only hire folks who physically reside in the US.
Senior Software Engineer, Member Growth: https://boards.greenhouse.io/omadahealth/jobs/3552347
Senior Software Engineer, Full Stack: https://boards.greenhouse.io/omadahealth/jobs/3360101
Other open positions can be found in https://www.omadahealth.com/careers
Omada Health is on a mission to inspire and engage people in lifelong health, one step at a time. We’re looking for Rails/React engineers to join our team and help build out our platform to support our members and to improve Omada's ability to reach out to more lives.
As a key member of our engineering team, you will help design, build and maintain systems necessary for rapid growth. Our team practices pair programming so you will have the opportunity to learn new techniques and share your skills.
Check out our press release here regarding the impact of personalized coaching to health outcomes: https://www.businesswire.com/news/home/20211026005385/en/Oma...
We can only hire folks who physically reside in the US.
Senior Software Engineer, Member Growth: https://boards.greenhouse.io/omadahealth/jobs/3552347
Senior Software Engineer, Full Stack: https://boards.greenhouse.io/omadahealth/jobs/3360101
Other open positions can be found in https://www.omadahealth.com/careers
> Incentivizing the failure to replace wear items is bad policy.
I see it as the least bad option out of the ones that we can field. Every kind of taxation policy will have pros and cons, and IMO the tire tax is potentially the one with the least amount of friction to implement and enforce.
(amount is from the rough average annual mileage of 13,500mi/year, assuming 30mpg, and the 82c/gallon tax).
The real solution is the one we've already been pushing for and have had a great amount of success over the years, which is to treat mental health issues with the same importance as physical health issues.
Edit: Just found out that Meetup.com is owned by WeWork. This makes sense to me now.
Disclaimer: I'm not saying that that's good or bad.
For me, I think it's from my underlying interest in being good at something without having to make compromises or handicaps. As a benign example, I rarely/almost never change the keybinds in any of the code editors that i've used because I like the idea of being able to competently use all of them in their default settings to have a consistent experience everywhere. This allows me to use another instance of VSCode/PyCharm/Eclipse/etc. that's not my own and be able to reasonably be productive in that instance. It's a little silly, but it's something that I like.
Tabs runs counter to that underlying interest to a very small degree. They're there to be customized, and there's an expectation that you are supposed to customize their appearance for each view that you use to view them if you want a consistent appearance.
To an extent, I view the debate between the two as something similar to the debate between configuration vs convention. Convention is great when you're working within the 99% of the use cases that it supports, but it becomes difficult for the folks who need to do something not supported by the built in conventions and vice versa. Some people like one, some people like the other as a matter of preference. However, there's a small subset of the population that basically need configuration for one reason or another to operate. Whether it's because you're building a product that needs a feature that the framework doesn't support to stay afloat, or in this case, they need to be able to customize the appearance of code on the screen easily to be able to perform their duties in a reasonable time. I don't know if this comparison makes sense or is reasonable.
I will say that i've ran into enough errors due to people entering tabs into places that they shouldn't that my hate for tabs has grown more than it should. This ranges from people somehow (via copy+paste or whatever) entering a tab into a form field that doesn't allow for it to other engineers doing something similar for code and causing weird issues.
Edit: formatting