HackerTrans
トップ新着トレンドコメント過去質問紹介求人

sudoshred

no profile record

コメント

sudoshred
·18 日前·議論
Petition to have the question added to leetcode. Two variants one with a single type of parens such as () and one with mixed parens (),{},[]. In each problem implement the map method which takes a chunk sequence of the overall input, the reduce method which takes an array of map method output for each chunk and returns the overall answer.
sudoshred
·18 日前·議論
Also consider RTS elements, like assigning certain schedulers to handle workloads which are swappable and tuneable, maybe with some skill tree unlocks.
sudoshred
·21 日前·議論
Same people complaining "no one wants to work these days".
sudoshred
·24 日前·議論
Depends. I can certainly offer to rewrite my old code that contributed to the memory shortage, for a price.
sudoshred
·先月·議論
Safety of their IPO
sudoshred
·先月·議論
Location: DC metro/Northern Virginia

Remote: Yes

Willing to relocate: Yes (continental US)

Technologies: TypeScript/Node, Python, Java, AWS, GCP, vector embeddings, ECS, SQS, DynamoDB, MongoDB, Datadog, CDK, Terraform, Docker, Kubernetes

Resume: https://drive.proton.me/urls/XKGXBP4BBW#qxa0grxxCT8c

Email: [email protected]

Senior Engineer most recently at Anywhere Real Estate (contacts platform, thousands of agents): designed and shipped duplicate contact detection using vector embeddings and weighted similarity scoring, replacing brittle boolean rules with fuzzy/near-duplicate matching that actually works on messy CRM data. Led a full redesign of async sync infrastructure—moved from Lambda to ECS, introduced a queue-backed worker pool (SQS + dedicated containers), and decoupled task execution via a shared worker contract. Took P99 enqueue-to-dequeue from ~5s to <10ms; cut peak queue ingress ~100× with producer-side backpressure. These patterns map directly to agentic workflows and human-in-the-loop automation at scale.

Before that: region build orchestration at Amazon (correctness invariants, async message passing, safer cutovers); ML-powered OCR and machine translation pipelines at The Bison Group (GCP Document AI + Azure Translator, scaled to 2,000-page docs, resolved >70 RPS throttling, zero-downtime API migrations); FHIR validation on Lambda at Cigna.

Comfortable owning ambiguous backend/AI feature work end to end—architecture, implementation, observability, rollout. I use AI tooling (Cursor, Claude, ChatGPT) heavily for design spikes, API scaffolding, and test generation, with review and monitoring before anything hits production.

Looking for: a team building something with real technical depth, where async/distributed systems or AI-enabled product features are central, not bolted on. Startup or growth stage preferred but not required. Open to fully remote or onsite/hybrid anywhere in the continental US—prefer to start remotely and happy to discuss relocation once we've established a good fit.
sudoshred
·先月·議論
Statistically impossible to inadvertently generate a collision using UUID keys. UUID is designed to be unique when generated across any computer system. Practically speaking if you have an exactly matching pair of UUIDs from disparate system you have found the exact record match. The name gives a hint "Universally unique identifier". -Not a cryptographer.
sudoshred
·先月·議論
sounds like a compliment to the implementation
sudoshred
·2 か月前·議論
Much like most office jobs
sudoshred
·2 か月前·議論
imminent danger pay
sudoshred
·2 か月前·議論
nearly retired
sudoshred
·2 か月前·議論
bitshifting screen renders directly to pixels on custom hardware, if I had to bet
sudoshred
·2 か月前·議論
Some people enjoy vendor locked managed services for their core infrastructure. Typically this decision is made when building from zero to one in resource constrained environments, and the long term play is to move to your own table/db when it becomes sustainable to do so. The only reason to move to a managed service after having done the work to setup self owned systems is when you need to either a) CYA or b) reduce headcount
sudoshred
·3 か月前·議論
Bite selection is akin to bin packing, now that I think about it.
sudoshred
·4 か月前·議論
You missed the killer feature, even more diffusion of responsibility.
sudoshred
·4 か月前·議論
"internet chum" is a good one, it echoes "slop bowl".
sudoshred
·4 か月前·議論
Essential is contextually defined by whoever implemented the that part of the front-end basically.
sudoshred
·5 か月前·議論
It not a killer feature, granted. I would be willing to bet that the cost of the engineering to develop and support this feature as a default capability for the fleet of all vehicles would be less than the value of energy saved ammortized over the lifetime of all relevant vehicles.
sudoshred
·5 か月前·議論
Intuitively appreciating that these "boring fundamentals" are the default bottlenecks is a aign of senior+ swe capability.
sudoshred
·5 か月前·議論
If it wasn't sold as the next big buzzword you could easily hire 10 new SDR employees who would sell it that way.