kgrandis

Parelio | REMOTE | http://parelio.com

Parelio builds software that helps medical device companies and their distributors make better decisions when it comes to managing inventory and surgeries. We are passionate about building an analytics-driven technical infrastructure that reduces waste and increases supply chain transparency. This lets all stakeholders make better decisions, which ultimately leads to more affordable healthcare for patients.

:: Senior iOS Developer ::

Details: https://parelio.recruiterbox.com/jobs/fk0hvol?referer=hn

:: Senior Rails Developer ::

Details: https://parelio.recruiterbox.com/jobs/fk0hvoc?referer=hn

Parelio | Durham, NC; or REMOTE | http://parelio.com

Parelio builds software that helps medical device companies and their distributors make better decisions when it comes to managing inventory and surgeries. We are passionate about building an analytics-driven technical infrastructure that reduces waste and increases supply chain transparency. This lets all stakeholders make better decisions, which ultimately leads to more affordable healthcare for patients.

:: Senior Software Engineer (full-stack, Python/Django) ::

Details: https://parelio.recruiterbox.com/jobs/fk0k2v?referer=hn

:: DevOps Engineer ::

Details: https://parelio.recruiterbox.com/jobs/fk0k2p?referer=hn

Parelio | Grand Rapids, MI; Durham, NC; or REMOTE | http://parelio.com

Parelio builds software that helps medical device companies and their distributors make better decisions when it comes to managing inventory and surgeries. We are passionate about building an analytics-driven technical infrastructure that reduces waste and increases supply chain transparency. This lets all stakeholders make better decisions, which ultimately leads to more affordable healthcare for patients.

:: Senior Software Engineer (full-stack, Python/Django) ::

Details: https://parelio.recruiterbox.com/jobs/fk0k2v?referer=hn

:: DevOps Engineer ::

Details: https://parelio.recruiterbox.com/jobs/fk0k2p?referer=hn

I thought about going that direction, but was concerned the birds might eat the pellets.

I didn't show the false positive video. :P There were some additional features thrown in, but for presentational simplicity I went with some strong, easy ones to explain. I think one thing helped keep FPs low was some frame-based signal thresholding. So, I required a significant squirrel signal (over multiple frames) before it went hot. That prevented any small FP blip to trigger the gun.

Thanks! You definitely made things much easier for me. I had also played around doing some raw ctypes work with OpenCV and now greatly appreciate your efforts.

Both really good questions. That was started almost two years ago so we've worked on a variety of different types of projects since that initial study--from simple websites to high-availability, rich applications. Some have required more internal knowledge of Django than others, but I can't think of a time where Django itself was an impediment or a bottleneck.

With regards to time series...me too! I don't have enough data to make any statistically-backed claims, but anecdotally Django-based sprints do start off with a big bump in velocity, because you're handed a tremendous amount of functionality upfront via the framework itself, Admin CRUD, etc.. Once a team gets moving their velocities tend to stabilize, which is one of the reasons story points and velocities are such powerful estimation and forecasting tools.

That being said, C# teams seem to have larger standard deviations around their mean velocity. One thing I have noticed is that refactors tend to have differing impacts. Major refactor efforts and rearchitecting almost always noticeably hit the C# team's velocity much more so than the impact on the Python group. Having done refactoring and and rearchitecting in both environments, I tend to think it's a function of the syntactical overhead associated with the C# language.