We're the authors of n2y. We use it extensively and it is quite robust at this point. It maps Notion content into Pandoc's AST and provides a plugin system for dealing with information that's not easily representable in the AST.
Congratulations on putting together such a nicely designed app. I definitely noticed the quick download time when I installed it to check it out.
I run a medical device software development firm. I'm a software engineer who has moved into the medical-device regulatory affairs. I've helped several software teams learn to develop (and document) software for medical devices.
Even if you're not planning to make the jump from a wellness app to a medical device for a while, there are some things you can start documenting now that will make the transition a lot easier for you when you get there. E.g., starting to track formal requirements (https://innolitics.com/articles/2022-04-27-design-inputs/) and tracing them to verification protocols (e.g., automated or manual tests).
We have a bunch of Notion templates that we use with our clients that I could share with you to help you get started. Feel free to email me at jdgiese AT Innolitics.com
We're a remote-only team of 14 software engineers helping accelerate progress in the medical device industry. Our founders are both biomedical engineers and software developers, uniquely positioning us to understand and implement our clients' needs. Investment in the medical device industry is booming due to COVID, and AI/ML is making its way into the clinic. It's a good time to be in this space and we expect to grow significantly over the next few years.
We're looking for a well-rounded engineer with web development experience to work with our clients, helping them write software for their medical devices.
Some technologies that we commonly use are Python, TypeScript, C++, Django, TensorFlow, and React.
The salary for the position is $95k - $125k/year, depending on ability and experience. We also have overtime pay and bonuses.
We're remote-only, respect work/life balance, and value on-going learning.
I don't follow this exact procedure, but I do something similar.
I have a bunch of external drives. They go back to ~100GB parallel-ATA drives in external USB enclosures. I think I have ~10 generations of disks in play right now. I've spent less than $2,000 on drives in ~20 years. I probably should have purchased a few more disks over the years since I went >18 months between generations and sometimes 24-30 months.
I wrote some simple scripts to copy the contents to a new drive, compare hashes of the copy to the source, and store the hashes for any new files on the new copy. It's mostly automated. The only thing I've thought about adding is perhaps using PAR2 to add some bitrot protection.
I keep the most recent disk at home and copy files to it throughout the year. (I keep it unplugged most of the time.) When I buy a new disk I run my copy scripts then take the old drive to a relative's house and store it in their gun safe. (Lately I've been the oldest drive from the safe and marveling at the old technology. >smile<)
30 years now in a more organized fashion, 40 years if you count disorganized.
Some of my older drives are no longer recognized by the drivers anymore.
I've had several drives completely fail, and one I dropped that never worked again.
I've used CDROMS, DVD-Rs, zip drives, and even cartridge tape for a while, but the hard drives work the best. I still have the cartridge tapes, but no way to read them anymore. Same with zip disks, can no longer read them.
We're a remote-only team of 12 software engineers helping accelerate progress in the medical device industry. Our founders, are both biomedical engineers and software developers. We've found some better ways of writing medical-device software that we believe will transform the industry. You can help us make this happen.
Investment in the medical device industry is booming due to COVID, and AI/ML is making its way into the clinic. It's a good time to be in this space and we expect to grow significantly over the next few years.
You’ll work with one of our clients, helping them write software for their medical devices. We usually follow an agile process and demo any notable progress to clients once a week. You’ll be responsible for gathering requirements from the client, architectural design, coding, testing, risk analysis, and documentation. You’ll also be responsible for reviewing other engineer’s code (and your code will be reviewed too).
Agreed! I live in NYC and don't drive too often. I just got back from a two-week trip with a car rental and was really surprised at how great Apple Maps was. The map design is nice and clean and it works well with CarPlay. I also felt like the audio instructions were very clear and easy to follow. E.g., "pass this light and turn right at the next one." I also liked the "Share your ETA" feature which I used a few times. Really nice job Apple!
Innolitics | Software Engineer | Remote (US except CA, HI, or AK) | Full Time | https://innolitics.com
We're a remote-only team of 12 software engineers helping accelerate progress in the medical device industry. We're doing this in a few ways: First and foremost, we help our clients write software for their medical devices. Second, we create tools to help startups efficiently navigate this highly regulated industry. Third, we share our knowledge through the articles we write.
Why would you want to work with us?
- meaningful work
- small, profitable, and growing
- many opportunities to learn new technologies
- talented and fun teammates
- work/life balance (and overtime pay)
Learn more about us, the job, and how to apply here:
We’re fully remote and have hired a few engineers out of college. They’re very independent and productive. Who knows if they’d be even better if they worked onsite, but I doubt it.
As I say, very different time. I didn't even really have email prior to entering the workplace and, while there were conference calls to manufacturing sites and the like and other (frequent) phone calls, it was a very in-person swing by offices/desks/labs sort of environment. But that's obviously different from what a fresh engineering grad has been exposed to.
The first half of the technical interview is practical questions like: "How does a browser's event loop work?". The second half is a live coding a solution to an algorithm problem. You'll finish the problem after the interview and submit your solution.
reply