Hacker Newsnew | past | comments | ask | show | jobs | submit | brikelly's commentslogin

Milestone Systems | Lead Data & AI Engineer | Remote (USA)

The Arcules team at Milestone is looking for a Lead Data & AI Engineer to design and evolve the intelligent analytics portion of our security cloud platform. This spans from squeezing the most out of video and data coming into our platform, to building scalable data pipelines, to deploying AI models and agents that power insights for our customers.

In this role, you’ll architect and implement our data lakehouse, transform existing data into high-value “gold” datasets for AI applications, and design the AI systems that bring those insights to life. You’ll work hands-on with cutting-edge technologies including Spark, Iceberg, Trino, Go, Python, and GCP.

Arcules is like a "reverse Netflix": our data pipelines process petabyte-scale incoming video streams, requiring close to real-time inference.

If you have experience building and deploying production ML systems and distributed data infrastructure, we'd love to hear from you! Milestone offers excellent benefits (23 days PTO, 6% 401k match, superb health insurance...) and an async-first remote culture.

Apply here: https://fa-ewto-saasfaprod1.fa.ocs.oraclecloud.com/hcmUI/Can...


Absolutely loving the importance and beauty of using gravity in this process.


It makes sense now, but I guess I spent my life thinking this kind of process was actually cutting and not grinding. Well TIL.


The stage before what was shown may involve actual cutting/sawing and or cleavage. https://en.wikipedia.org/wiki/Cleavage_(crystal)

This allows you to preserve material for making multiple gems where grinding can only result in a single piece.


Arcules | Principal Engineers + Senior Eng. Managers | Full-time | USA | Remote | https://arcules.com

Arcules builds cloud and hardware solutions for commercial video cameras and IoT devices. Our eng team of 70+ is growing, and we need the nerdiest of nerds to join us! (Oh and yeah, we need our Eng Managers to be just as nerdy ;)

If you have an insatiable technical curiosity, love working remotely, devour and deliver constructive feedback, and want superb benefits, this is the place for you.

Our stack is K8s, Golang, C++, React, GCP. We love optimizing for flow and outcomes, and look forward to doing that with you too!

Apply now at: https://go.arcules.com/careers


It's interesting to me that the industry still relies so heavily on diffs of code listings as a primary method for code reviews.

It is absolutely a good use of a human reviewer's time to build a mental model of the code's runtime behavior. But to do that by manually by reading each line and trying to predict what will happen when it's run is massively inefficient, incomplete, and error-prone. Plus it's susceptible to the "LGTM, fine, just merge it" phenomenon when the PR is large.

Reviews of static code listings won't reveal how ORMs structure their DB queries at runtime, or reflect how dynamically injected/configured components will behave, or any other number of things that are only visible by watching the code execute.

We have commoditized linting, checking for CVEs in dependencies, and static analysis for certain classes of bugs. We should now use fast runtime analysis in the same flow to relieve the burden from human reviewers of having to do line-by-line "telepathy reviews" where they try to magically divine how something will run in production at scale. (Full disclosure, I work at a company doing exactly that - https://appmap.io - and one of our most popular features is our sequence diagram diff that shows runtime differences between a PR and the main branch).


It’s not exactly what you’ve asked for, but “Principles of Product Development Flow” by Don Reinertsen is a seminal work that covers a lot of queuing theory in the context of software development and project management.


Sequence diagrams are great, but creating them by hand is a pain. It's not just manual toil, they also go out of date. AppMap (where I work) can generate them automatically based on runtime analysis of an application: https://www.youtube.com/watch?v=8l4-hNih_GQ


Partial-hour time zone offsets (like in Nepal or St. John’s Newfoundland) were a big learning moment for me back in the day.


This is why things like https://sustainabledev.org/ exist. It’s far too easy to fall into the busyness trap and burn out.

Things managers can do to prevent this include:

- using a pull model of work flow

- enforcing WIP control

- using employee vacations to find bus factor problems (“hey, Brent was OOO for 2 weeks and these things were stuck, let’s fix that…”)

- creating a culture where backpressure to management is strongly encouraged


AppLand - Ruby Internals Expert - FT (preferred) or contract - Remote [USA / CAN / EU / UK]

AppMap is one of the world’s leading Autonomous Software Development tools. Thousands of developers already use AppMaps to visualize complex applications and automatically find issues that human code reviewers cannot spot.

AppMap provides the missing data within the software development lifecycle, delivering immediate feedback to developers in their editors that, until now, was only available after deploying to production.

AppMap supports many languages, including Ruby. Our integration hooks into the Ruby VM to record application interactions and functions, and must always do so without affecting its behavior, integrity, or performance. We are growing our Ruby team, and so we need more Ruby experts to help!

There are thousands of Ruby programmers in the world today. But here at AppLand, we’re not looking for any normal Ruby engineer. We need someone who is an expert on the internals of Ruby and how it is interpreted and executed at runtime. Someone who knows the difference between YARV and MRI. Someone who has a commit history within the Ruby core. Someone who has worked on profilers, tracers, or debuggers. Someone who enjoys the world of bytecode as much as they do writing an elegant Rails app.

If you’re that person, please get in touch at jobs@app.land. When you write to us, please tell us about the thing that you love (or hate!) most about the internal architecture of Ruby’s implementation.

https://appland.com/


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: