I was working on the Fuschia project at Google and we used Gerrit as well. It definitely took some getting used to, but once I got the hang of it I found it to be a much better review tool.
It was a lot easier to show how contributions stacked, to continue iterating on a “branch” while waiting for a review from the team, and worked better with trunk-based development workflows.
Consultant with experience as a software engineer at various enterprise-scale tech companies including Google and Amazon (AWS). Looking to help companies of all sizes solve business problems (often through automation and code) as a core-contributor or part-time CTO.
___
For early-stage startups, I typically focus on:
• Improving the time to market of feature development by evaluating the software delivery pipeline and investing in minimal viable release tooling.
• Increasing customer satisfaction by improving operational resiliency, thereby increasing service reliability
• Managing risk by choosing the right tools, establishing low-friction security best practices, and standing up essential monitoring tools.
___
For more mature startups, I typically focus on:
• Reducing the total cost of ownership of a product by addressing critical technical debt and lowering engineering overhead through automation, optimizing cloud compute resources, identifying optimizations in data storage solutions, and leaning on robust open source software.
• Reducing attrition through a combination of technical and operational practices inspired by the engineering culture at Google.
• Anticipating increased demand by designing modern elastic software architectures that can efficiently scale in and out to meet the complex needs of most established tech products.
I’m in the process of scaling up my consultancy, and I have a client right now who’s looking to add a major feature to their product with a strict early fall timeline.
I’m open to candidates with a variety of experience, but would ideally like someone relatively senior with strong frontend experience. For this project, the ideal candidate would have (at least one):
• Experience with Vue.js or similar framework
• Experience with Python and AWS Lambda
• Expert with Microsoft SQL Server
Looking for someone who can onboard quickly to new projects, read technical documentation, and contribute largely asynchronously. Also looking for someone who’s comfortable being utilized intermittently. The project is in-progress, but I’m still getting up to speed and defining areas that I would like to delegate, so it may be a few weeks before I can effectively bring someone on.
To apply, send me a copy of your resume, portfolio samples, or anything else that you think demonstrates your fit for the role. I’ll do my best to respond quickly. If you’re not a fit at this time, I’ll keep you in mind as I continue to scale into other projects.
Cool project! I'm a jazz musician / software engineer and have been building a similar personal project in my free time, writing a deterministic algorithm to perform harmonic analysis on popular standards, with the end goal of having an interface that could suggest chord substitutions to the user. I'm also looking at indexing all the tunes so the user can fuzzy search for tunes with similar chord progressions.
I'm curious to see how well you think the GPT solution works for you (I'm having trouble trying it because I'm so far back in the queue. Congrats on all the traffic!) My suspicion is that it would struggle to capture more nuanced substitutions, because it doesn't really have the underlying context (things like harmonic tendencies of individual notes and voice leading) to draw from but I've been surprised before. Hope I can try it next week!
The output produced by GPT is mostly on point. However, it does makeup stuff sometimes. A fine-tuned or smaller model trained on music theory data is the way to go in the future. Your app sounds interesting. Please share whenever you can!
Ex-Google, Ex-Amazon software engineer with experience at various other enterprise-scale companies. Looking to help companies build and scale their products with robust operational resiliency, either as a core-contributor or part-time CTO.
-- Python / NodeJS / Rust / Go --
Differentiators - I specialize in helping small to medium startups improve their development and release processes, and fortify their operational resiliency. This may take many forms, from straightforward improvements to CI/CD and testing, to more sweeping architectural changes aimed at pre-empting scale and cost complications. I have not seen every problem (nor do I believe I’ve seen most of them), but from a broad set of experiences and deep research in the field of software system design, my clients enjoy immediate and lasting impact towards their company’s goals. When I encounter something that is orthogonal to my experience, I draw from my diverse network of industry experts as an investment in MY business, at no cost to my clients. I bill for my time solving client problems, not learning new skills, and as a consequence only accept work when I believe there’s a good fit.
I have a passion for - building data-intensive applications. I enjoy speccing out larger architectural migrations for existing software or designing backends to leverage workload-optimized datastores for the unique demands of different components of a distributed system. I also thrive at getting the most performance out of monolithic storage systems when optimizing more for developer ease. Though the bulk of my services are typically done entirely asynchronously, I enjoy being available for collaboration and mentorship when it can benefit my clients and their teams.
For recent clients - I’ve been working on importing cloud resources into infrastructure as code, building custom development/testing frameworks, creating dynamic templates for code generation, building out initial CI/CD, enforcing coding standards, setting up change management processes, and migrating resources into a multi-account AWS Organization per the AWS SRA specification. All of my projects are left with exceptional amounts of FAANG-inspired documentation (both for continued development and maintenance). I treat each piece of work as I’d want it handed off to me.
It was a lot easier to show how contributions stacked, to continue iterating on a “branch” while waiting for a review from the team, and worked better with trunk-based development workflows.