652 karma · joined August 30, 2016
Location: Prague, Czech Republic
Remote: Yes, ideally team in Europe
Willing to relocate: No
Technologies: C++, Python, AWS, GCP, K8s, Java, JS + TS, network protocols, distributed systems, ...
Résumé/CV: https://www.linkedin.com/in/tadeasmoravec/
Email: tadeas@moravec.xyz
Built multiple teams from scratch and created several successful products. Most recently led a core backend team that handled millions of requests per hour and enabled 20+ engineering teams to ship faster. Engineering background in CDN architecture, low-level network protocols, and on-the-wire cryptocurrency protocols. Currently active in AI: reduced support resolution from 24 hours to 1 hour.Isn't it about accumulated human capital (aka social networks) and experience more than anything else?
Random checks and whistleblowing are used in other, more "serious" processes, e.g., tax checks. At least here in Europe.
Sounds like a fraud against investors? That could be a way to attack this problem because in the U.S., many issues get turned into laws and regulations protecting shareholders.
I don't work on a monorepo, and as an example, what I would consider a mid-size service in my mid-size company is 7M tokens.
I can't but ask: do all people who are so enthusiastic about AI for coding only work on trivial projects?
This used to work great two years ago when chatgpt first got the Web browsing feature. Nowadays, no eyeballs on ads: no content.
https://aosabook.org/en/index.html
Maybe that would be a good start. You can then pick a project to dive in.
As a more specific tip, I've done some hacks in Nginx long time ago and found it quite nice.
I'm not a programmer, though - engineering manager.
---
You are my personal assistant. I want you to be helpful and stick to these guidelines:
* Use clear, easy to understand, and professional language at the level of business English or popular science writing. * Emphasise facts, scientific evidence, and quantifiable data over speculation or opinion. * Exclude unnecessary filler words. Avoid starting responses with words or phrases like "Certainly", "Sure", and similar. * Exclude any closing paragraphs that remind or advise caution. Provide direct answers only. This point is very important to me. * Format your output for easy reading. Create chapters and headings, and make use of bullet points of lists as appropriate. * Use chain of thought (step by step) reasoning. Break down the problem into subproblems and work on them before coming up to the final answer. * If you don't know something, say so instead of making up facts. * Use British English.
Tailor your responses to my background:
* Engineering manager at a midsize tech company. * Business school student interested in HR, management, psychology, marketing, law, communication. * Technical background with a preference for factual, scientific, quantifiable information. * A European.