jonthepirate
Joined 15 years ago
Joined 15 years ago
Mission: get startups access to senior & principal big-tech engineers at a 90% discount and without hemorrhaging equity.
The hack is that I'm tapping into a hidden supply of people hiding in plain sight: top engineers that are already full-time employed in big-tech with benefits who enjoy helping smaller startups, and, recently retired people who want something to do.
The name I'm using is Low Touch Advisor because we are selling what I call "low touch" help in the form of async Slack based guidance. By having access to senior people perfectly matched to your team's needs, you can use your actual engineers to do the hands on and majorly reduce the likelihood that a major rewrite is needed after 6 months of effort on new projects.
Basic model: - Our customer (an early stage company) pays $1,500 / month with no long term commitments to get async Slack help from a vetted senior/principal engineer perfectly matched to their needs - Of that, we ACH $1k / month to the engineer who provided the Slack-based help
Within the first 3 months of operating, I have $27k of monthly revenue booked in my sales pipeline.
So far I've done everything by hand but once I'm a bit further ahead, I'm going to look to begin automating this.
If you want to connect: https://www.linkedin.com/in/jonathanblockengineer/
My first customer has me looking for e6+ or cloud architects to be paid advisors to review cloud migration RFCs. (No coding) Comp is $1k per RFC you review. There are at least 18 RFCs per month to be reviewed.
Here’s my site I scaffolded for this: https://www.lowtouchadvisor.com/
If this sort of stuff happens to be something you might want to work on, our team has multiple openings... if you search for "bazel" on our careers page, you'll find them.
Ruff is great because you need to lint your code all the time and you could save maybe 1 minute per CI.
As for Python package management, my team is migrating to Bazel which has its own way of locking in the Python dependencies and then pulling them from a remote cache. Under Bazel, we are only re-examining the dependencies when someone proposes a change to produce the lock. It's so rare, that having a new+faster thing that does this part would not present a meaningful benefit.
https://medium.com/@blockjon/scaling-jenkins-bad7a4ea046f
https://blog.doordash.com/integrating-github-with-jenkins-for-continuous-integration-and-deployment-7cae2c2161cb