168 karma · joined November 1, 2017
On the backend, use web API security best practices. This means only allow API access to authorized devices and/or users. Keep your database secure. There’s tons of resources out there about how to build a secure backend.
Cybersecurity isn’t nearly as complicated as marketers and would-be consultants paint it out to be. Granted, programs are complicated (firmware especially), so invest heavily in good testing to catch insecure code before they manifest into issues.
As far as the FDA is concerned, document everything, probably more that you think is necessary. Write up a clear set of requirements, verification and validation plans, and very thorough design documents. This benefits both them and any future team members that may need to work on the project.
There’s also engineers that prefer doing these different kinds of work. They thrive on quick wins and kudos from founders. Early engineers probably need to be ok with bugs and edge cases that they’ll never go back and fix. Personally I don’t like doing work like that, but I’m definitely in the second class of engineers who needs systems to be modular, composable, and well defined.
Honestly I really disliked the audiobook. The reader was dreadfully drab, even with his impeccable English. Also the book ended up costing me $60 ($15 / mo Audible subscription), even I technically got to listen for free. Most expensive history lesson I've ever paid for.
The political climates that existed during the colonization of the Americas played an important role in the evolution of modern cultures. The book is filled with examples of different societies and how they formed, and politics has played a role in ever single instance. Regardless of if you agree with the authors’ ideologies or not, they do a pretty good job of remaining neutral when examining historical evidence. I found it a nice change of pace from the typical “westernized” explanations of how civilizations (especially Native Americans) were structured.
Overall I think it’s an excellent read, well worth the investment.
Overall though regular .ts code works well. We use it for all our API definitions and networking layer, and it’s been 1000x better than our former version built with jinja/jQuery.
I found my singing teacher through a Google search, and I found my violin teacher through word of mouth.
Singing is a wonderful skill and an amazingly unique instrument. Good singing requires awareness of the lungs, diaphragm, pelvis, butt and often (if you're like me and play guitar while doing it) the upper body.
The lower pay isn't low - I'm making plenty for the Bay Area. The stress isn't too high - we have important customers with product expectations, so we test thoroughly before we release changes. I may not be in the weeds writing code every week because I need to wear the product and QA hats too, but overall I love being a high impact player on a team making an impact in a market I care about. Whether the company takes off or doesn't, I'm happier building something with minimum overhead and maximum flexibility.
For packages to avoid, stay away from Celery. It's just... icky.
I hope you find peace and healing. People often suck, but they can also be beautiful if given the chance. And you deserve that chance.