Sofia Silva

268 posts

Sofia Silva banner
Sofia Silva

Sofia Silva

@StaminaLoops

👩‍💻 VP Engineering @remote 👩‍⚕️ Former MD

Katılım Nisan 2015
371 Takip Edilen438 Takipçiler
Sofia Silva retweetledi
ElixirConf Europe
ElixirConf Europe@ElixirConfEU·
Excited to announce @remote as a Gold Sponsor for ElixirConf EU 2026! Building global HR solutions for distributed teams. Thank you for supporting the community. #sponsors" target="_blank" rel="nofollow noopener">elixirconf.eu/#sponsors
ElixirConf Europe tweet media
English
0
2
11
1.8K
Sofia Silva retweetledi
José Valim
José Valim@josevalim·
Lately I worked on compilation times for Elixir (and all BEAM languages). TL;DR: * Elixir v1.20 compiles ~10% faster on OTP 28 and ~20% faster on OTP 29 * Boot times on BEAM is roughly 10% faster on OTP 29 * A new interpreted mode in Elixir v1.20 compiles up to 5x faster 🧵👇
José Valim tweet media
English
6
21
216
9.9K
Sofia Silva retweetledi
Nikunj Kothari
Nikunj Kothari@nikunj·
My only advice to CEOs this year.. Hire tinkerers. Make it high status. Find ones that will explore the edges and (ideally) naturally gifted at teaching people. Empower them to freely roam across the org and fix large problems that can be automated. All your execs will complain that these tinkerers don’t understand scale or systems (rollout being a favorite word). Listen, and ignore them. Or even better give them budget to hire a tinkerer to achieve their targets. Give these tinkerers ambition, purpose and hard targets and watch them fly.
English
225
421
4.1K
230.3K
Sofia Silva retweetledi
LangChain
LangChain@LangChain·
@remote is automating complex HR data migrations at scale with a Code Execution Agent built on LangChain + LangGraph. By combining LLM reasoning with sandboxed Python execution, they're: • Transforming thousands of employee records into structured schemas in hours vs. days • Eliminating hallucinations by keeping large datasets outside the context window • Making migrations repeatable and auditable for sensitive compliance data across global jurisdictions Read the full guest post: blog.langchain.com/customers-remo…
LangChain tweet media
English
2
5
49
4.6K
José Valim
José Valim@josevalim·
Today we celebrate 15 years since Elixir's first commit. To mark the occasion, we shipped an early release candidate for Elixir v1.20 which has TYPE INFERENCE FOR ALL CONSTRUCTS.🎉 In the latest article, I break down the next ~15 weeks and the challenges for the next ~15 months.
English
25
110
571
33K
Sofia Silva retweetledi
Addy Osmani
Addy Osmani@addyosmani·
This is the most fun moment to be a developer in years. The AI tools are imperfect, the patterns are still emerging, and there's genuine room for experimentation. Roll up your sleeves and build something. The earthquake is further opening up what's possible. The best news about this new layer: traditional engineering skills are more valuable than ever, not less. It helps us minimize shipping slop. Developers who already invested in CI/CD, testing, documentation, and code review are having the most success with AI tools. These "boring" foundations are accelerators. They turn agents from chaos generators into productivity multipliers. The real opportunity is learning to work at a different altitude. Instead of typing syntax, we're reviewing implementations, catching edge cases, and shipping features in hours that used to take days. That's genuinely exciting. Yes, there's a learning curve. Understanding how to provide context, iterate on plans, and review AI-generated code quickly takes practice. But this is learnable through doing - build small tools, review everything, develop intuition through repetition. The multiplier potential is real when you combine AI speed with engineering judgment. We're not replacing coding skills but we're finally able to focus them on the interesting problems while delegating the tedious parts.
Andrej Karpathy@karpathy

I've never felt this much behind as a programmer. The profession is being dramatically refactored as the bits contributed by the programmer are increasingly sparse and between. I have a sense that I could be 10X more powerful if I just properly string together what has become available over the last ~year and a failure to claim the boost feels decidedly like skill issue. There's a new programmable layer of abstraction to master (in addition to the usual layers below) involving agents, subagents, their prompts, contexts, memory, modes, permissions, tools, plugins, skills, hooks, MCP, LSP, slash commands, workflows, IDE integrations, and a need to build an all-encompassing mental model for strengths and pitfalls of fundamentally stochastic, fallible, unintelligible and changing entities suddenly intermingled with what used to be good old fashioned engineering. Clearly some powerful alien tool was handed around except it comes with no manual and everyone has to figure out how to hold it and operate it, while the resulting magnitude 9 earthquake is rocking the profession. Roll up your sleeves to not fall behind.

English
82
218
1.8K
362.8K
Sofia Silva retweetledi
Anthropic
Anthropic@AnthropicAI·
New on the Anthropic Engineering Blog: Long-running AI agents still face challenges working across many context windows. We looked to human engineers for inspiration in creating a more effective agent harness. anthropic.com/engineering/ef…
English
150
373
3.4K
1.5M
Sofia Silva
Sofia Silva@StaminaLoops·
@andreasklinger @marcelolebre @Jobvo @remote Partly. We made mass updates to the inline endpoints specs using Cursor, and that required LLMs because it involved inference that a script couldn’t handle. Then we generated code with a script. It was a strong experiment, and we will write it up
English
0
0
1
39
Andreas Klinger 🦾
Andreas Klinger 🦾@andreasklinger·
@marcelolebre @Jobvo @remote feels like an important information but tbh - unsure why - i would feel better if cursor would write a codemod and then this would do that amount of changes deterministically
English
1
0
2
121
Job
Job@Jobvo·
Yesterday an engineer at @remote ran a single prompt in cursor touching ~2400 files. Took ~16 hours, but worked. The secret was a massive markdown file as prompt with examples and clear instructions
English
25
3
109
46.9K
Sofia Silva retweetledi
Remote
Remote@remote·
@Workday + Remote Expanded partnership set to eliminate payroll complexity. Workday GO Global Payroll. Coming very soon. ⚡ 👉 okt.to/DyLej9
English
43
72
94
22K
Sofia Silva retweetledi
Marcelo Lebre
Marcelo Lebre@marcelolebre·
I rarely celebrate but @Jobvo and I have been quietly building the backbone for modern global payroll and we finally get to share it. @remote will power @Workday global payroll - beautifully crafted infrastructure and powered by next-gen AI. The future of payroll is here.
Marcelo Lebre tweet media
Remote@remote

@Workday + Remote Expanded partnership set to eliminate payroll complexity. Workday GO Global Payroll. Coming very soon. ⚡ 👉 okt.to/DyLej9

English
23
43
114
25.6K
Sofia Silva retweetledi
José Valim
José Valim@josevalim·
Elixir v1.19 released: enhanced type checking, broader type inference, and up to 4x faster compilation for large projects! elixir-lang.org/blog/2025/10/1… A huge thank you to Fresha, Starfish*, and Dashbit for sponsoring the type system, plus @CNRS and @Remote for making it possible.
English
7
120
574
31.8K
Sofia Silva
Sofia Silva@StaminaLoops·
Our codebase compiles ~55% faster with Elixir v1.19.0-rc.2!
José Valim@josevalim

Elixir v1.19.0-rc.2 is out! It is our last stop before v1.19, so please give it a try: elixirforum.com/t/elixir-v1-19… The results are great: the @remote folks confirmed their codebase compiles 55% on v1.19 and type checking is still ~1ms/module on average, even with all new features! We worked really hard on this one! @duboc_guillaume and I had to go beyond the current state of the art to optimize some key operations used during set-theoretic typing checking! We will publish some articles on this later on. Enjoy!

English
3
5
118
12.1K
Amir
Amir@HassanBashich·
@StaminaLoops Any insights on how and why it's such a massive improvement?
English
2
0
0
244