IceCreamYou
Joined 15 years ago
Joined 15 years ago
Can you imagine writing software with no debugger or logging, and you only get to run it every few weeks? That's what building hardware is like for many product companies. At Instrumental, we're building a manufacturing optimization system that collects data no one else can, and uses machine learning and visualizations to automatically identify defects and help product companies understand their assembly processes.
With ~35 people we are a small but mighty team with a collaborative, friendly culture. We value an inclusive environment and actively work to promote diversity in our team.
We also value good tools. For example, I manage the web app team - our deploys involve running a single command and take just a few minutes, so we deploy frequently and with confidence. "Watch mode" compilation usually takes under a second. We have "branch environments" to test any pull request in a production-like environment with real data. And we have robust tests.
Open roles:
- Senior Backend Engineer, Platform: https://jobs.lever.co/instrumental/4c155db0-8506-4096-ae7d-c...
- Senior Backend Engineer, Web App: https://jobs.lever.co/instrumental/317d0eb2-e2db-498a-b79c-6...
- Senior Full Stack Engineer, Factory Software: https://jobs.lever.co/instrumental/9d9cee6e-a0b2-4484-8171-7...
- and others at https://instrumental.com/careers
Can you imagine writing software with no debugger or logging, and you only get to run it every few weeks? That's what building hardware is like for many product companies. At Instrumental, we're building a manufacturing optimization system that collects data no one else can, and uses machine learning and visualizations to automatically identify defects and help product companies understand their assembly processes.
With ~30 people we are a small but mighty team with a collaborative, friendly culture. We value an inclusive environment and actively work to promote diversity in our team.
We also value good tools. For example, I manage the web app team - our deploys involve running a single command and take just a few minutes, so we deploy frequently and with confidence. "Watch mode" compilation usually takes under a second. We have "branch environments" to test any pull request in a production-like environment with real data. And we have robust tests.
We're hiring for basically every engineering role: backend, frontend, systems, SRE... apply online: https://www.instrumental.com/careers
[1] http://helloanselm.com/2014/github-pages-redirect-performanc...
Then I tweeted about it, and Addy Osmani responded[2] pointing out that Chrome does in fact support multiline consoles with its Snippets[3] feature. It's still kind of obnoxious, but it does the job.
[1] https://github.com/IceCreamYou/Chrome-BigConsole [2] https://twitter.com/IceCreamYou/status/354181339408375809 [3] https://developers.google.com/chrome-developer-tools/docs/au...
https://pmarca-archive.posterous.com/the-pmarca-guide-to-sta...
Obviously there are some ways to fail that are much more common than others, but those tend to be based on lack of action, e.g. failure to actually ask users if they want to use your product before building it. There is plenty of material on those common sorts of failures, it's just usually phrased constructively, i.e. "how to do SEO" rather than "we died because we posted duplicate content on every page of our site."
[ my public key: https://keybase.io/icecreamyou; my proof: https://keybase.io/icecreamyou/sigs/m4RuTNMO9gUwLoa5kweLND-ZErRstABDqoFB7lz2uzk ]