If you're an engineer and want to go deeper into the core algorithms behind genomics, there's a book / course called Bioinformatics Algorithms. It was a punishing read when I was going through it a few years ago (but rewarding). It's probably much better now given the state of AI.
That hasn't been my experience. Bambu's documentation, including the guides and wiki, is disjointed and inconsistent. You'll often find contradictions between pages or information that isn't appropriately fleshed out. Sometimes bits and pieces on a topic are spread across several wiki pages and guides. You'll also find that there's now an increase in AI slop in some of the introductory guides (e.g., tons of emdashes and sentences that don't seem to make sense).
Having the printer give you reminders to do something doesn't mean that maintenance is minimal.
> She had no desire to learn the ends and outs of 3d printers. She wanted something easy to use and reliable. The Bambu Labs printer I bought her has been just that.
Where is this coming from? You absolutely need to know the ins and outs of a 3D printer. Nozzles wear out, build plates wear out, components need to be regularly cleaned properly and lubricated, you have to keep filaments dry, certain filaments can only be used with certain components, you constantly tweak slicer and temperature settings, ... The list goes on.
3D printers, including Bambu Lab printers, are definitely not easy to use nor are they reliable. They're maintenance heavy. Sometimes you have to do a print multiple times because it'll fail for a myriad of reasons. Maybe you oriented it wrong, maybe your slicer settings are off, maybe it didn't have proper supports, maybe the filament is messed up, ...
I'm also in the same boat of regret, but for other reasons. Their support team is beyond awful. I purchased an H2S AMS combo just shy of two months ago (mostly because I saw it being praised by HNers a while back) and found out recently that the AMS they've sent me is defective. It's been truly a bizarre experience trying to deal with customer support. They told me to disassemble the AMS and swap a couple of modules that they mailed me. I did, provided them evidence that I did, and provided evidence that it didn't fix the problem. Their response was to claim that I didn't actually swap the modules and that because of that my warranty no longer applies, and then they said they'd give me a free roll of filament for my troubles (lol). At that point I began the process of invoking the consumer protections afforded to me. Called my credit card company and opened a dispute, invoked Massachusetts law M.G.L. c. 93A, and I'm about to contact my AG.
It's a shame they're going in such an anti-consumer direction, both with their gaslighting customer support and the lawfare against Orca.
This is such a strange take. Your words remind me of past crypto hype cycles, where people pushed web3.0 and NFT FOMO hysteria.
Engineering is
the practical application of science and mathematics to solve problems. It sounds like you're maybe describing construction management instead. I'm not denying that there's value here, but what you're espousing seems divorced from reality. Good luck vibecoding a nontrivial actuarial model, then having it to pass the laundry list of reviews and having large firms actually pick it up.
I wonder if we'll reach a breaking point with public forges, where they'll simply reject hosting a repo if it isn't from someone with a vetted background or if it detects hallmarks of LLM slop (e.g., many commits over a short period of time or other LLM tells).
I've been a software engineer for over 15 years, working on everything from APIs and financial models to data pipelines and firmware. Beyond the technical stuff, I’ve led small, tightly-knit teams, managed projects, mentored and advocated for colleagues, and spent a lot of time communicating technical concepts to folks who aren't as tech-savvy.
Now that I'm authorized to work for any U.S. employer, I'm hoping to pivot to a smaller company where I can make a stronger impact. I'm open to any field, but particularly drawn to life sciences. It's been an area of interest for me ever since going through a bioinformatics algorithms textbook cover-to-cover, and the hope is that I can continue learning about the life sciences space while providing value with my existing skill set. Like many on HN, I have a heartfelt drive for learning, whether through books, courses, shadowing experts in the field, or jumping head-first into unfamiliar situations.
If you're doing anything in biopharma, computational biology, medical devices, synthetic biology, or anything along those lines, by all means please drop me an email. If you're working in some other unrelated field, still don't hesitate to reach out — I'm always interested to know what folks are working on and if I'd be able to help move things along in any way.
http://github.com/offbynull