🛠️ Software Development consultant (see https://xitter.cf/t.co/kTbNt4SJc5) 🎥 Short tips https://xitter.cf/t.co/CqhBJEf2SE 🎙 @elixir_friends
USA
Joined January 2013
- Tweets1.9K
- Following366
- Followers3.1K
- Likes2.7K
Pinned Tweet
For the first time in a while, I have an opening for new clients (in September).
Do you need help with your product, engineering team, or an Elixir/Phoenix project?
How I help teams:
- ✨ Product: building the best possible product for your customers. I care about the solution end-to-end.
- 🧑💻 People: strengthening your team's technical and product skills as we improve the product (remember, your team is the engine behind your product). Mentoring, pair programming, workshops, whatever is needed to make your team the best version of itself.
- ♻️ Process: continuously improving how your team builds, coordinates, and delivers your product
Through it all, I practice and teach a culture of continuous improvement so that, long after I'm gone, your team can continue the virtuous cycle of self-improvement.
DMs are open, or email me at german(at)germanvelasco.com
For more on how I work, you can see germanvelasco.com
#MyElixirStatus #ElixirLang
I'm considering organizing AI mastermind groups for software devs.
So much is happening, but what’s actually working? All that info is siloed, and we're all re-learning the same lessons.
So, something like this:
- 3-4 people per group
- Meet every two weeks
- Share what’s working and what isn’t
Is it a good idea or a terrible idea? 😆
German Velasco retweeted
If coding agents will write most of our code, what happens with our communities and sense of ergonomics? How does it impact our compilers and tools?
German Velasco retweeted
The keynotes at @ElixirConf showed the Elixir community matured a lot when it comes to AI practices within the last year:
* Quinn Wilton discussed the importance and accessibility of applying formal methods and static analysis in the age of AI
* Chris McCord highlighted that last year coding agents could barely run for 20 minutes and today it can run for 20 hours non-stop. You should be stress testing, optimizing, running verifications way more frequently than before. Furthermore, as coding agents own more of the software development cycle, runtime observability becomes part of the loop (something Erlang/Elixir excels at) and will be super valuable (see screenshots)
* Zach Daniel closed with hands on steps to adopt agents throughout and around your software development lifecycle
The keynotes are all on YouTube: youtube.com/@codesync?si=5fw… enjoy!
Who's going to @ElixirConf in a couple of days? I'd love to meet up!
#MyElixirStatus
Makes me unreasonably happy when people enjoy using a library I created.
Thanks for writing this Mike! 🙌
✏️ Phoenix's LiveView test helpers require you to hand-build the form payload and start a fresh pipe after every click.
phoenix_test writes the entire flow as a single pipe from the user's point of view and fails with a focused error. #ElixirLang
mikezornek.com/posts/2026/9/…
I've always heard it said, "Niche down!" But that never felt right to me. Instead of niching down, position yourself. 👇
germanvelasco.com/blog/dont-…
German Velasco retweeted
I'm looking for Elixir consulting, so I've built a low-risk offer to reach new faces.
Two weeks. One problem. $6,000 (discounted rate). One nagging thing: flaky tests, a stalled upgrade, a Sentry backlog.
A share or intro means a lot 🙏
mikezornek.com/elixir-consul…
#ElixirLang
This blog post by @whatyouhide is amazing. The best explanation of GenStage I've seen.
andrealeopardi.com/posts/gen…
But even that post mentions `max_demand` and `min_demand` as "the thing that trips people up the most".
It made me think: why is that?
I think the reason for that is that `min_demand` is not a true counterpart to `max_demand`. Even GenStage's docs explain it correctly:
":min_demand specifies the minimum threshold to trigger for more demand"
I think if we renamed `min_demand` -> `min_threshold` or `resupply_threshold` it would remove some of the confusion that max & min demand bring.
#MyElixirStatus
Clearly meant PhoenixTest 😬
Just published Phoenix 0.12.0! 🎉
Excited for this one because it now supports `aria-label` and `aria-labelledby`
Thanks to contributors for making it happen! 🥳
phoenix-test.hexdocs.pm/Phoe…
#MyElixirStatus
Just published Phoenix 0.12.0! 🎉
Excited for this one because it now supports `aria-label` and `aria-labelledby`
Thanks to contributors for making it happen! 🥳
phoenix-test.hexdocs.pm/Phoe…
#MyElixirStatus
German Velasco retweeted
German is awesome to work with. Don’t miss this opportunity!
For the first time in a while, I have an opening for new clients (in September).
Do you need help with your product, engineering team, or an Elixir/Phoenix project?
How I help teams:
- ✨ Product: building the best possible product for your customers. I care about the solution end-to-end.
- 🧑💻 People: strengthening your team's technical and product skills as we improve the product (remember, your team is the engine behind your product). Mentoring, pair programming, workshops, whatever is needed to make your team the best version of itself.
- ♻️ Process: continuously improving how your team builds, coordinates, and delivers your product
Through it all, I practice and teach a culture of continuous improvement so that, long after I'm gone, your team can continue the virtuous cycle of self-improvement.
DMs are open, or email me at german(at)germanvelasco.com
For more on how I work, you can see germanvelasco.com
#MyElixirStatus #ElixirLang
I keep finding that the diverge-then-converge pattern is really helpful with LLMs. So, I wrote a post about it.
Hope others find it helpful!
✍️ germanvelasco.com/blog/diver…
German Velasco retweeted
For the first time in a while, I have an opening for new clients (in September).
Do you need help with your product, engineering team, or an Elixir/Phoenix project?
How I help teams:
- ✨ Product: building the best possible product for your customers. I care about the solution end-to-end.
- 🧑💻 People: strengthening your team's technical and product skills as we improve the product (remember, your team is the engine behind your product). Mentoring, pair programming, workshops, whatever is needed to make your team the best version of itself.
- ♻️ Process: continuously improving how your team builds, coordinates, and delivers your product
Through it all, I practice and teach a culture of continuous improvement so that, long after I'm gone, your team can continue the virtuous cycle of self-improvement.
DMs are open, or email me at german(at)germanvelasco.com
For more on how I work, you can see germanvelasco.com
#MyElixirStatus #ElixirLang
German Velasco retweeted
part one of "Why Software Factories Fail" hit 250k views in under 24h - now you get to enjoy part two
Love this post! 🥳 Lines up with what I've been seeing and trying to understand in the industry. (also love the workflow outlined -- matches so much of how I work). So much good stuff.
the post in question github.com/humanlayer/advanc…
my current plan is to break it up into two posts but this feels wrong
What are companies in the #ElixirLang space struggling with right now? AI adoption? Finding product-market fit? Team dynamics? Hiring? Something else? (I know there's varied answers, but curious if there are commonalities)
I'm not a big fan of the big-upfront-plan approach to work with LLMs.
Am I the only one?
I wrote a bit about it in germanvelasco.com/blog/are-p…
German Velasco retweeted
We’re hiring for my team in Berlin - come work with me! grnh.se/ncny3822teu
I finally finished writing the blog post that shares a few reflections and things I tried while creating ExCrap (some good, some bad) without reading the code.
✍️ germanvelasco.com/blog/i-wro…
#ElixirLang #MyElixirStatus
Just published a new library to calculate CRAP metrics (I know, that's what it’s called 🤷): change risk anti-patterns.
It’s a metric composed of cyclomatic complexity and test coverage. 👇
ex-crap.hexdocs.pm/readme.ht…
#ElixirLang #MyElixirStatus