We’re building a national ICHRA platform at the intersection of healthcare, fintech, compliance, and AI.

Implementation is getting cheaper. Engineering judgment is not.

We’re looking for engineers who enjoy:

* Turning ambiguous problems into production systems. * Owning outcomes, not tickets. * Working across product, architecture, and implementation. * Reviewing and improving AI-generated code. * Shipping quickly without creating a maintenance disaster.

Requirements:

* Strong Python, TypeScript, or equivalent experience. * Strong engineering judgment. * Strong communication skills. * US residency.

Apply: https://engineering.kyra.health

Questions: n@kyra.health

We’re building a national ICHRA platform at the intersection of healthcare, fintech, compliance, and AI.

Implementation is getting cheaper. Engineering judgment is not.

If you enjoy turning ambiguous business problems into production systems, owning outcomes, and shipping quickly without creating a maintenance disaster, we’d like to talk.

Python, TypeScript, healthcare, fintech, AI.

Apply: https://engineers.kyra.health Questions: n@kyra.health

We believe there is a significant opportunity to improve healthcare quality and cost for employers, employees, and insurance companies; regulatory changes and LLMs mean it is time to build. We think we can provide a better experience for less money, and have multiple positive impacts on society. We have the idea, the funding, and the skills and knowledge to make it happen. We're looking for a few more strong engineers to help us build it.

Responsibilities

- Research, plan, scope, and design solutions to difficult problems while navigating laws, regulations, and standards in money movement and healthcare.

- Produce elegant and simple code that is architected and written for the long haul.

- Speed up overall development efforts.

- Help build a development environment and operational tooling that will be the envy of companies many times our size.

Must Haves

- Strong Python or TypeScript skills, or a strong background in another dynamic language.

- A burning desire to get things out the door and in the hands of users.

- Strong communication skills.

Reach out to me at n@kyra.health, or kick the process off at https://enghiring.kyra.health

We believe there is a significant opportunity to improve healthcare quality and cost for employers, employees, and insurance companies; regulatory changes and LLMs mean it is time to build. We think we can provide a better experience for less money, and have multiple positive impacts on society. We have the idea, the funding, and the skills and knowledge to make it happen. We're looking for a few more strong engineers to help us build it.

Responsibilities

- Research, plan, scope, and design solutions to difficult problems while navigating laws, regulations, and standards in money movement and healthcare.

- Produce elegant and simple code that is architected and written for the long haul.

- Speed up overall development efforts.

- Help build a development environment and operational tooling that will be the envy of companies many times our size.

Must Haves

- Strong Python or TypeScript skills, or a strong background in another dynamic language.

- A burning desire to get things out the door and in the hands of users.

- Strong communication skills.

Reach out to me at n@kyra.health, or kick the process off at https://enghiring.kyra.health

We believe there is a significant opportunity to improve healthcare quality and cost for employers, employees, and insurance companies; regulatory changes and LLMs mean it is time to build. We think we can provide a better experience for less money, and have multiple positive impacts on society. We have the idea, the funding, and the skills and knowledge to make it happen. We're looking for a few more strong engineers to help us build it.

Responsibilities

- Research, plan, scope, and design solutions to difficult problems while navigating laws, regulations, and standards in money movement and healthcare.

- Produce elegant and simple code that is architected and written for the long haul.

- Speed up overall development efforts.

- Help build a development environment and operational tooling that will be the envy of companies many times our size.

Must Have

- Strong Python or TypeScript skills, or a strong background in another dynamic language.

- A burning desire to get things out the door and in the hands of users.

- Strong communication skills.

Reach out to me at n@kyra.health.

We believe there is a significant opportunity to improve healthcare quality and cost for employers, employees, and insurance companies; regulatory changes and LLMs mean it is time to build. We think we can provide a better experience for less money, and have multiple positive impacts on society. We have the idea, the funding, and the skills and knowledge to make it happen. We're looking for a few more strong engineers to help us build it.

Responsibilities

- Research, plan, scope, and design solutions to difficult problems while navigating laws, regulations, and standards in money movement and healthcare.

- Produce elegant and simple code that is architected and written for the long haul.

- Speed up overall development efforts.

- Help build a development environment and operational tooling that will be the envy of companies many times our size.

Must Have

- Strong Python or TypeScript skills, or a strong background in another dynamic language.

- A burning desire to get things out the door and in the hands of users.

- Strong communication skills.

Apply at https://www.unlaunchedhealthcarestartup.com/, or reach out to me at njl@njl.us.

The allocated money is then passed to the rights holders, based on the percentage of listens they received within users in that pool. Individual rights holders can negotiate additional bumps, and Spotify has some exceptions for what needs to be counted.

I know that the idea that money should go from a listener directly to the bands that user listens to, instead of splitting up the pool, feels like a pretty interesting one. Unfortunately, folks who listen to a lot of music tend to listen to smaller and more interesting bands as well. This change wouldn't necessarily result in more money in the pockets of smaller artists; it's not inconceivable at all that the rich would get richer.

It's also worth mentioning that the average person who spent money on music at all, prior to the invention of streaming, spent far less annually than they spend on streaming now.

I think artists are reacting to a lot of issues. The entire music industry is built around signing absolutely disgusting contracts with deeply talented and fundamentally naive 18 year olds who are effectively replaceable by the next new thing. This is compounded by the fact that most artists don't have a relationship with Spotify; they have a relationship with their record label who has a relationship with Spotify, and the label isn't really interested in giving an artist a full accounting of what they've brought in from Spotify.

Finally, and most importantly, there is a real disconnect between the social impact of music and the actual size of the industry. There's a lot of money there, sure, but the music industry is like a professional sports league in terms of total revenue. A few superstars are going to suck up a lot of the money and not leave much for the bench players, let alone the folks three leagues down from the "show".

The simple hubris in this statement is jaw-dropping. “Just a flag and a few if clauses! Easy peasy!”

GDPR blows up a lot of assumptions we make about writing software and managing servers.

https://www.privacy-regulation.eu/en/article-17-right-to-era...

GDPR is a wonderful idea that will be insanely expensive to comply with, act as a continuous drag on developing new technologies, and end up offering only nominal protection to end users. This is just going to be another way for EU regulators to smack around Google and Facebook. They probably deserve it, but the potential fallout for the rest of us is really going to hurt.

Don’t get me wrong, treating user data with respect is the right thing to do. But we’re all going to be paying for this overly broad and under specified legislation for years to come.

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

Points: 68

# Comments: 80

The answer feels trivial to me, which means I'm probably missing something. Fixed term for a few decades from the creation of the work, maybe 30 years or 40 years. After that, you need to give a copy of the work to the Library of Congress, pay a nominal fee, and you get a 5 year extension. Take as many of those as you want.

This greatly simplifies everything. If you find a work that is older than the base term, you look it up in the copyright extension database. If it's in there, you can find out who owns the rights to it, and try to license rights. If it isn't in there, it's public domain. If somebody doesn't stay on the ball enough to renew their rights every five years, it probably isn't all that commercially valuable, and moves into the public domain.

Rather than saying certain categories of animals should have the same rights as humans, maybe we'd be better off saying certain categories of animals deserve a higher level of ethical and legal consideration.

Doob is the man, and I was disappointed when I hit the spiral button and it was a demo of putting the things in a spiral, not the half-remembered spiral-esque model in my mind.

[1] http://en.wikipedia.org/wiki/Alternative_periodic_tables