Missed Nombas ScriptEase, a 90’s-era commercial runtime most famous for allowing JavaScript to operate the James Webb Telescope. http://brent-noorda.com/nombas/us/index.htm
The "in related news" story in this article is way more interesting, someone who apparently feels pretty strongly about running a pirate radio station.
- FCC is proposing $80,000 fine against a man in Oregon for operating an FM pirate radio station since 2018
- first complaint was in 2018, agents tracked it down, warned the man, and he gave them his transmitter
- second complaint in 2019, agents tracked it to the man's new home, they warned him again, he gave them his transmitter
- 2 stern warnings wasn't enough, because third complaint came in 2022, agents tracked it to the man's home again, the man's wife gave them 2 tranmitters
- the man then posted many videos on Facebook about his pirate radio station, and dared the FCC to lock him up. He then started another pirate radio station
> the nofly csv is almost 80mb in size and contains over 1.56 million rows of data. this HAS to be the real deal (we later get confirmation that it is indeed a copy of the nofly list from 2019).
I've used a recruiting company https://www.facet.net/ that also handles contract work, and works with a lot of startups. They can add you to a mailing list to send you opportunities that match your criteria.
Weave provides the leading SaaS "integrated communications" system (VoIP phones integrated with CRM, Google reviews, payments, scheduling, customer texting, analytics) for small businesses like dentists, vets, optometrists, plumbers, etc.
Backend is all Go running on modern infrastructure supported by a strong Platform Engineering and SRE team (i.e. you will spend more time coding than managing infrastructure). More about that here https://engineering.getweave.com/post/weave-devs-dont-do/
One of the people I managed on a remote team suddenly died one night from an aortic aneurysm. He was in his early 40's, had his teen-aged daughter living with him (who fortunately was away visiting her mom). I'd talked to him only hours before. I'd only met him once in-person, just a few weeks before, when he and I and another person I managed had an informal "on-site". I'd learned recently the two of them had been really good friends for many years.
The company had never had to handle something like this. Thankfully, HR and execs had the right priorities - concern for his family, respect for him and his family in how the news was shared with co-workers (especially with cause-of-death being unclear at first), concern for how it would affect close co-workers and others in the company, awareness that people would need to process and grieve in their own way.
HR talked with the family and got their permission to make an announcement to co-workers, and some guidance on the wording. HR offered to send this, but I felt that would feel too impersonal. I wanted news like that to come across in the most personal way possible, from someone (like me) who knew and cared for him.
The amazing response from the company was a big part of the healing. So many people wanted to do something. The family decided to have a private ceremony, and asked that instead of flowers, donations be made to an animal charity his daughter loved. People really felt for his daughter, and wanted to send cards and letters (which the family was happy to support). One of the teams (that hardly knew him) decided to have a commemoration during their weekly meeting.
The hardest part of all of this was (a) when his daughter called me to arrange for return of his work equipment and (b) when a family member suggested that one way I could help would be to share some of my experiences with his daughter about working with her dad. I have girls of the same age, so pretty close to home. It was hard to write that letter (#b), but it was also healing for me to think about the many positive ways he'd affected me and our team.
A few days later, it felt right to me to have some "closure". I sent a note to the company thanking everyone for the different ways they had respectfully honored our co-worker and supported his family. I also shared some of my memories working with him, and how much I missed his contagious happiness. As sad as it was that he wasn't with us anymore, I wanted to remember how much fun it was to work with him, and that's what I was going to focus on.
I hope I won't have to go through that again any time soon, but when I do, I hope it goes this well.
Ambra Health (https://ambrahealth.com) | REMOTE (USA), Full time | Java/Linux engineer, Medical Image Processing and Storage
At Ambra Health we help the health care system solve complex problems with storing and sharing medical imaging data (X-rays, CT's, etc), at locations around the world - including many renowned health centers. This involves managing a lot of medical data, getting it to the right place quickly and reliably over the Internet - some very challenging and interesting engineering problems.
We are looking for a Java developer with Linux experience to join our remote-only image storage engineering team. This team works on the storage and image-processing services of our platform, which manage over 10 billion images (4PB) in the cloud and in data centers around the world. The ideal candidate would be able to work independently with minimal supervision, seasoned to make good productivity/coding/architecture decisions.
Requirements:
- Java development for back-end REST services
- Basic Linux system administration skills
Big plus if you've got these skills:
- Building server software with multi-threading and concurrency, in a distributed network environment
- Experience with DICOM medical file format, other medical standards, or image processing
- Diagnosing application problems in a Linux environment
Our hiring process is pretty painless - short introduction call, 1-hour call with the team to get to know each other, then (if it works for you) a paid part-time trial period to see if we like working together.