JobFluent

The Best Tech Jobs in Barcelona & Madrid.

[Nacho González @nachog]

HIRING IN PUBLIC: añadida esta pregunta en el apply tras ver el BAJISIMO NIVEL de uso de IA en peña de CONTENIDOS/MKT 1/2 >>

[GeeksCAT @Geeks_CAT]

L'Open Source Fest evoluciona!

L'esdeveniment de la comunitat tech en català es transforma: neix la #GeeksCATConf!

Mateix esperit geek, comunitat més forta i un format renovat. Dev, sistemes, IA, ciberseguretat... t'hi esperes?

🎟️ Detalls i entrades: https://t.co/IFj6rZ5h8C

[Madrid Elixir @MadElixir]

Próxima charla en el meetup de Elixir Madrid: El camino de Elixir hacia el tipado estático gradual por José Luis Esteban Aparicio https://t.co/d7XBhWct1u

[Elisenda Bou-Balust @elisenda_bou]

Where is capital flowing? https://t.co/eyWSD714ZT

[Madrid DevOps @MadridDevops]

Este mes de junio tenemos Madrid DevOps: un evento presencial el día 10 a las 18:30 #devops #claude #madrid_devops https://t.co/6AoAAUXYlF

[David Sacks @DavidSacks]

Q: How are job postings for software engineers rising rapidly despite AI agents automating coding?

A: Because there’s far more code to manage than ever before. We’re already seeing a 14x YoY increase in GitHub commits, and it’s accelerating.

AI has dramatically lowered the cost of writing code, so it’s now being used across far more businesses, applications, and use cases.

We’re at the beginning of a massive productivity boom driven by the proliferation of bespoke software throughout the entire economy.

Coding has been AI’s breakout use case this year. The fact that it’s increased demand for software engineers — rather than decreased it — should call into question the entire “AI will cause mass job loss” narrative.

[Nacho González @nachog]

Si buscas perfiles A, dedica el mismo tiempo a hablar con referencias que hablar con el candidato. 1/2 >>

[David Bonilla @david_bonilla]

No era consciente de hasta que punto OpenAI era el líder indiscutible del nicho. Que vale que Anthropic es un cohete de Albacete y su curva de demanda se está aplanando, pero sigue a años luz de otros competidores como Google.

[Carles Reina @Carles_Reina]

Mega excited to be officially launching @ElevenLabs Spain today. My home country and one of the fastest growing markets for us. Let's go!!

[Full Stack Vallès @FullStackValles]

Recordeu, és aquest dimecres!
Parlarem dels CVs, las Cover Letters, el mercat que coneixem i el mercat ocult.
Comentarem situacions reals que ens donaran pistes de com actuar. Apunta't aquí 👇🏽

[Full Stack Vallès @FullStackValles]

Hola! S'acosta el darrer dimecres d'abril, i sabeu això que significa oi? Doncs que tenim trobada de Full Stack Vallès! Com sempre, a l'@ateneuCandela , i en aquesta ocasió tenim una xerrada fora de lo habitual 👇

[mitsuri @0xmitsurii]

Steve Jobs talking about hiring professional management- it didn't work at all.

[Elixir Jobs @jobs_elixir]

Senior Elixir Software Engineer @ Kantox / On-site / Remote #job #MyElixirStatus #elixirlang https://t.co/rgiw5KM2Mv

[Pao Ramen @masylum]

In the last two years, the #1 thing people have asked me was how I hired at Factorial.
I've shared my playbook again and again, so I decided to write it once and for all.

It got… long. So I turned it into a 3-chapter series on Fika.

Enjoy!

https://t.co/YYdbNdpGvT

[Y Combinator @ycombinator]

Paul Graham on why startup teams can outperform big companies: "small groups can be select."

[Nacho González @nachog]

Vamos allá: Álvaro y yo montamos empresa y buscamos >>> Full-Stack Engineer, Co-founder (40k-60k€ + 10-20% Equity) AI Native / Voice Agents Startup [React/NodeJS] <<< [Se agradece RT!] Info/Transparencia Salvaje >> 1/n

[Tom Johnson @tomjohndesign]

This is how I feel about vibe coding.

Any project I try that has any kind of complication has this immediate burst of progress. Things are amazing and it feels like a superpower. Then... as I add more complexity, things crash to a halt.

The only projects that I think I can create are ones that fall in this "vibe zone". Prototypes, UIs, products—anything that's simple and has low complexity fits right in that zone. Proof of concepts, interactions, stuff like that. The tools are able to make things that fit in that slot.

But.

Everything falls to pieces as that complexity curve increases. And the problem is that any good product design process has increasing complexity. A basic prototype turns into a good prototype as soon as it has layered interactions, transitions, good affordances, hover states, 1000 tiny little details that make something feel correct and real.

The benefit of vibe coding is supposed to be that you move fast and you can whip things out—letting AI do all the work for you. The problem is it loses steam as soon as the necessary complexity is added. It keeps redoing itself, rewriting code, affecting things that are unrelated and then causing other issues.

But if you add that complexity, every vibe coding session quickly turns into a whack-a-mole bug-bashing session.

I'm not sure the solution to this. With traditional prototyping the solution is to duplicate, add more complexity, create more frames/scenes, tweak, fork, etc.

However with vibe coding, one little prompt can destroy literally everything. There's a stage where I end up walking on prompt eggshells-- trying not to give it too much or too little context so that it doesn't go rogue and break everything.

There's only a few exceptions to this. @cursor and @framer.

I can make great progress with Cursor, give it narrow context, and I have to approve the edits that it makes. This feels like a correct workflow. The problem is, I can't see the thing that it's making because it's an IDE, not a visual environment. Yes, I can create local builds and refresh my browser and all that kind of stuff. But the visual aspect is totally lost from the coding experience. It's a developer tool.

Framer gets this right because it only allows narrow updates within a single component on the page. Yes, it's limiting because it can only do a single thing at once, but at least it's not trying to create the entire page from scratch and manage it all through a prompt interface.

These seem like the right approach.

@Cursor: Allow the AI to edit anything but allow the user to approve those edits and see them in context.

@Framer: Allow the AI to only narrowly edit a single file or component to keep the complexity down to a minimum and reduce catastrophic edits.

I'm optimistic that tools like @Figma, @Lovable, @Bolt, and @V0 can make cool prototypes, but I just keep running into walls when it comes to doing anything more than just a basic interaction prototype. They need to do less IMO.

Hopeful that those tools add more controls that are in the same line as Cursor and Framer. I'll also add that this is similar to how we do it with @Basedash chart generation as well. But we're not a vibe tool in the normal sense so the parallels are a little bit harder to draw.

[David Baratech @davidbaratech]

🚨 BREAKING: Google pierde tráfico por primera vez en su historia.
Wikipedia también. YouTube también.

¿Estamos presenciando el fin de Internet tal como lo conocemos?

Un thread sobre lo que NADIE está hablando (pero debería) 🧵👇

[Internal Tech Emails @TechEmails]

Elon Musk: "The OpenAI Company"

December 11, 2015

[Project Europe @ProjectEurope_]

Let's change the narrative 👀

https://t.co/CArzKKkO0j