Rafting on HN, never thought I'd see the day! For anyone looking for more on the subject of multi-day wilderness rafting trips, my parents wrote a blog post on a similar trip we did in Alaska (more remote and logistically complicated, less significant whitewater-wise): https://www.roguewanderers.com/blog/chilikadrotna-river-floa...
Had the opposite experience recently as an EM. Spent a few months trying to find a staff-level engineer. Found a great candidate who worked for a FAANG, worked to get our budget up to his expectations, sold him on the team, and he accepted our offer with a start date 6 weeks in the future so he could have time to wrap up his work. Fine, I'm just happy to have filled the role after an arduous search. A few weeks go by, and he hasn't responded to my "we're excited to have you join the team, etc" email or any HR emails about filling out his paperwork. I call and email, the recruiter calls and emails, nothing. We never hear from him again..
He's been active on social media so we know he's alive, and assume he parlayed our offer into a raise somewhere else. Ok, that happens, but to accept an offer and totally ghost? Jeez. I could have used those intervening weeks to interview more candidates had he just sent me a quick note, now I've got to backfill his position while also trying to fill the new ones that just opened... I guess hiring is a shitshow from both sides sometimes.
browser compatibility is hard :). in all seriousness though, we're working to support every browser we can. hopefully we'll have some fixes for Linux users in the next couple of days
We should mention this on the site, but the visualizer currently only works in Chrome due to some idiosyncrasies with the way other browsers handle (or don't handle) getting waveform data from audio tags. We're working on it though!
Yes, we're using Express.js. QUnit looks interesting, I think I'll start with it. Is it pretty standard to just have an HTML file that runs all your client-side tests?
Does anybody have recommendations for where/how to start learning best practices for TDD?
As (nominally) top nerd at a tiny startup (2 engineers), I feel like I should set a precedent sooner rather than later for testing. This is currently not possible since I don't know anything about it, so any resources would be appreciated :)
Edit: Primarily looking for resources involving Node.js and client-side testing of a jQuery-based website.
Agreed, the current state of software tools for biology is sad- the tools are written by scientists, for scientists, and tend to have messy source code and incomplete/difficult to read documentation.
I don't mean to insult the people who work on the tools currently- they're great! But we need more software people writing tools for the industry.
Fortunately, people are starting to do just that. TeselaGen and Genome Compiler are both good examples. (Disclaimer- I'm a TeselaGen engineer)