rolgalan
rolgalan.bsky.social
rolgalan
@rolgalan.bsky.social
I usually post about engineering processes, development productivity and anything related to software industry, with a particular interest in Android.
«If European regulation were so ineffective, why did the Trump administration go so far as to threaten bans and sanctions against European regulators who dared to implement digital laws? Precisely because effective regulation is seen in Washington as a direct obstacle to US technological supremacy.»
November 9, 2025 at 5:49 PM
«Dismissing European concerns about technological sovereignty as “Cold War thinking” misreads reality. This isn’t ideological competition — it’s economic warfare where technology is a national weapon built through political and industrial choices.»
November 9, 2025 at 5:49 PM
«When Europeans use “our” digital services, we’re actually using American infrastructure governed by American law for American interests.»

«The argument boils down to this: Everyone uses AI, but Silicon Valley or Beijing decides what AI exists, which values it encodes and which interests it serves»
November 9, 2025 at 5:49 PM
«Like any optimization effort, cost optimization requires good data. If you don’t have data, start there. See if you can gather accurate data about the cost of running the technical solutions but also how that cost maps to the revenue generated.»
October 26, 2025 at 2:52 PM
«Create reports that highlight how technical projects, initiatives, strategies and improvements impact business metrics. Present these findings in terms understandable to non-technical stakeholders.»
October 26, 2025 at 2:52 PM
«Principal Engineer is the voice of the customer in the engineering room and the voice of engineering in the business room»
blog.alexewerlof.com/p/principal-...
Principal Engineer
The level after staff engineer
blog.alexewerlof.com
October 26, 2025 at 2:52 PM
Based on these findings it’s fundamental to carefully review any code produced by LLMs, ensuring you fully understand it before submitting it to production.

Engineers need to remind that they are still responsible for the code submitted and have clear understanding of the generated code.
October 26, 2025 at 1:12 PM
«The variance in structural metrics suggests that the choice of an LLM has significant consequences for a project’s long-term maintainability, irrespective of the model’s functional performance. This indicates that different architectural philosophies and training data result in varied outputs».
October 26, 2025 at 1:12 PM
«A defect rate that includes a 5-8% chance of being a bug and a ≈2% chance of being a security vulnerability is significant. This finding underscores that LLM-generated code, even when it passes functional performance tests, is not immediately suitable for production environments.»
October 26, 2025 at 1:12 PM
«Although LLMs can generate functional code, they also introduce a range of defects, including bugs, security vulns, and code smells. These defects don't appear to be isolated; rather, they may represent shared weaknesses stemming from systemic limitations within current LLM code generation methods»
October 26, 2025 at 1:12 PM
«The “senior” in the title does not mean more years of experience. After all, “year” is fundamentally the wrong unit of measurement for exp. The “senior” part carries more expectations, larger scope, and longer time horizon. This requires a different toolbox to deliver higher impact, and at scale.»
October 18, 2025 at 9:16 AM
«The higher level translates to fewer opportunities and time to work hands on with the code»

«As a Senior Staff Engineer, I rarely see the immediate impact of the initiatives I’m driving. It feels more like building a staircase than climbing a step at a time.»

blog.alexewerlof.com/p/beyond-sta...
Beyond Staff Engineer
Some call it "Senior Staff", some "principal", others "technical director", but what comes after Staff Engineer? What are the challenges and toolset to handle higher complexity across a larger organiz...
blog.alexewerlof.com
October 18, 2025 at 9:16 AM