mjulian
Joined 12 years ago
Karma
313
Submissions
14
Member since
Dec 30
Recent submissions
Comment · 1 year ago
Comment · 2 years ago
Stealth | San Francisco, CA (hybrid: M-W-F ONSITE) | Full-time | Backend Engineer
We're building a product in the cost management space (yes, another one), but this one is being built by the founders of The Duckbil Group (Corey Quinn & Mike Julian), an AWS-focused cost management consultancy.
We're looking for someone to join as second engineer to help build out the product. Mostly looking for backend expertise. Past experience with AWS billing or Clickhouse are a huge bonuses.
Tech stack: Python (Flask), React, Typescript, Postgres, Clickhouse, AWS
We can sponsor the transfer of an existing visa but cannot sponsor the creation of a new visa.
You can apply here: https://duckbillgroup.typeform.com/to/LSRU50mB
Comment · 6 years ago
Yeah, we're investigating what's going on with this. Seems there's a bug in the public price list we're trying to work out.
Comment · 7 years ago
Corey's business partner here. I can attest: it does not. I sometimes wish it would...
Comment · 7 years ago
I recently interviewed a clinical psychologist who specializes in burnout about this on a podcast recently: https://www.realworlddevops.com/episodes/avoiding-treating-b...
The main takeaways: spend way more time with friends and family, get (back) into your hobbies, and take a very solid break (2+ weeks).
Comment · 7 years ago
I love the product, but the login workflow is awful. Why innovate on logins? We've solved that problem.
Specifically, the login is a randomly-generated one-time code sent to your email address. Notion says this is more secure than them storing a username+password, but that's a dubious argument. They've also said this is two-factor auth (lolno). A side effect of this is that Notion is unusable on my mobile device since I have no email on it.
I really hope they implement a more traditional login system. Until then, I'm sticking with Evernote. :(
Comment · 8 years ago
He gets linked here pretty regularly, but for those who don't follow him, the author runs an email newsletter that's basically him throwing shade at AWS every week. It's fucking hilarious AND useful.
Comment · 8 years ago
Bit of shameless self-promotion here, but I'm the author of Practical Monitoring. Among other things, I set out to answer exactly this question. Check out Part 2 (Chapters 7, 8, and 9 answer your question specifically). https://www.practicalmonitoring.com/
Comment · 9 years ago
SEEKING WORK / SF Bay Area / Remote preferred
I'm a DevOps Engineer/Site Reliability Engineer/Operations Engineer/whatever they're calling it these days with about 15 years in the industry. I've got a broad skillset for all sorts of projects and needs: automation, deployment, orchestration, scaling, you name it.
I'm primarily a monitoring specialist, though: I'm the author of O'Reilly's upcoming Practical Monitoring and the editor of Monitoring Weekly (https://weekly.monitoring.love). Besides writing a book on monitoring, I'm architect-level when it comes to designing and deploying monitoring strategies for SaaS companies.
You can find me at:
Website: https://www.asterlabs.io LinkedIn: https://www.linkedin.com/in/miketjulian/
Comment · 9 years ago
Thanks for mentioning Monitoring Weekly! We're super happy you're enjoying it. - Mike (one of the curators of Monitoring Weekly)
Founded by myself and Corey Quinn of The Duckbill Group/Last Week in AWS, we're building a cloud cost management product based on our six years of experience consulting directly in the space for hundreds of clients.
We're looking for a full-stack or backend engineer to help us build the early product. There are three other engineers on the team already. We've got solid distribution via our existing clients, multiple design partners, and a clear roadmap.
Stack: AWS, ClickHouse, Python+Flask, React+Typescript.
Past experience working on cloud cost tools, whether at a vendor or internally, is a huge bonus. If not already in San Francisco, we'll help with relo. Email your resume to [email protected].