Quick Answers & Second Opinions

Forward the error text or stack trace that has you stuck; a senior engineer will explain it and name the first thing to check.

Deliverables include

• A plain-words account of what the message is telling you
• The two or three likeliest culprits, most common first
• The first check to run, spelled out ready to paste
• Whether this smells like a one-off or something bigger

Send us a build quote or a proposal, and we will put on paper whether the money asked suits the work described.

Deliverables include

• Our verdict on the price against that scope: low, fair, high
• What is missing that later arrives as extra invoices
• Three to five sharp questions to send the supplier
• Commercial clauses worth resisting: code ownership, hosting lock-in

Tell us which technical choice has you stuck, and we will set down in writing which way we would go in your shoes.

Deliverables include

• A recommendation that names an option instead of hedging
• The three or four things that actually settled it for you
• The fairest argument we can make for the option we rejected
• What circumstances would flip the answer, so this can be reopened

And 1 more on the service page.

One proposed change, up to 400 altered lines, gone over by a senior engineer, who leaves written comments ready to act on.

Deliverables include

• Line-level comments across the change, 400 altered lines at most
• The verdict at the end: merge, merge after changes, or wait
• Each comment marked: blocker, nice-to-have, or our taste
• The ways this could fail that nobody has accounted for

And 1 more on the service page.

Send a month of your cloud billing across and we will point at the lines that look wrong, with a rough value on fixing them.

Deliverables include

• One month of your provider's billing, read through
• 5 entries that look most doubtful, with our reasoning
• A monthly saving put against each of them
• Whether your spending is typical for this sort of workload

And 2 more on the service page.

A read of your engineering advert and your interview stages, showing why good candidates keep dropping away before the offer.

Deliverables include

• The advert rewritten to be honest and specific, not aspirational
• Which stated requirements matter, and which frighten people off
• The interview sequence reviewed, and a shorter one proposed
• A take-home task cut back to 2 hours

And 2 more on the service page.

Half a day inside your repository by a senior engineer, written up as a plain account of its condition and the risks that count.

Deliverables include

• A 3 to 4 page report, with nothing padded out
• A maintainability rating, and the reasoning that got us there
• The 3 risks that matter, each costed and sized
• Notes on test coverage and how current the libraries are

And 2 more on the service page.

An hour on your architecture with a senior engineer who has read your material first, plus written notes and a recommendation.

Deliverables include

• A recorded 60-minute call with one of our senior engineers
• Time spent beforehand working through whatever you send us
• Notes afterwards, with a recommendation and the reasoning behind it
• Each option weighed, with its trade-offs set out

And 2 more on the service page.