This sounds like a great story, congrats! Having the opportunity to go "all in" on a hobby in this way is enticing for sure. Would you mind telling more about how the opportunity came up to go full-time? Was it being in the right place at the right time, or what type of risk did you step into?
Interesting approach, thanks for the good reads. Would love to support, no strings attached, if you see an opportunity. Reached out on LI, feel free to dump the request if this feels off to you.
Situational awareness is in fact a teachable/learnable skill and not just a "thing you have". Every professional field has one or another concept of the around it. I'd even go as far as saying it's one of my crucial (soft-)skills and has benefitted me greatly in my career, so it's great to see that I'm not alone with my interest in the topic.
As someone currently dabbling in the space, this is great reality checklist for a majority of research papers (and, unfortunately, a large majority on commercial endeavours, too) on the topic. The author makes a solid delivery on his outset promise.
It just might help to shed some light on something akin to the blockchain/machine learning hypecycle bubbles amongst startups.
Location: Munich, Germany
Remote: Yes
Willing to relocate: No
Technologies: Linux, Python, Kubernetes, all the things DevOps, MLOps
Résumé/CV: https://www.linkedin.com/in/benediktkoller/ or https://benkoller.de/assets/CV-Benedikt_Koller.pdf
Email: contact at benkoller dot de
---
I'm a DevOps guy at heart turned manager and founder of open-source MLOps tooling. I've scaled from 30 to 230, from 5 to 50 and most recently from 0 to 5. Along the way learned to love hiring/mentoring teams, building purpose-driven tech stacks, solving challenges data-driven and with a people-and-result-centered culture.
I wish you the best of luck and see a short-term need, but as someone deeply entangled into gastronomic subculture I would hate to see the experience of being hosted by a gastronomer and gastronomic team fade away. Going to your favourite restaurant or to a new, "fancy" place is just as much an experience in hospitality as it is in culinary.
Interesting to see that they relied on random forests for feature selection. I'd wonder if a more "classical" approach would have yielded similar/comparable results, or if these findings where only correlatable due to the use of ML.
> Instead of creating a single modality i.e. artificial noses or ears, medicine would benefit from a multimodal sensory system that uses vision, smell, auditory and perhaps even taste, _in conjunction_, as the human body is rich with signals through all these modalities.
Thats a great thought right there. Adding an over-time perspective would make this even more powerful, as a lot of information is encapsulated in change, not just absolute observation.
I wonder how much of the required sensing tech is already available, but most likely not rated for medical usage yet.
> If you too much shit to do, a calendar wont fix that. If your meeting are fucked because people are badly prepared, a calendar wont fix that. If you have to many appointments with your parents in law, your calendar wont fix that.
Couldn't agree more. People > Process, both ways around.
Great approach. I've been running ops teams for a long time, and eventually all teams have ended up spending some time optimising our CI tooling to involve some degree of caching - so you definitely are on to something.
Before I clicked your pricing I'd really wished for an affordable pricing plan to run this on BYO resources, but only your enterprise plan seems to cover this. I always get an iffy feeling when I have to build my software on external resources I have 0 control over. Your downtime will prevent teams from shipping their code - but I guess that thought is part of your upsell to the enterprise plan.
Anyway, it's one of these ideas I'd wish I had years ago, so congratz to you.
Definitely! It might sound like a sales-thing to say, but PyTorch in general is a huge point on our roadmap, but we’re not 100% sure what the most logical approach is. To keep the APIs consistent will involve some fiddling on our end.