Pol Gasull

#COP29 twitter.com/sageuk/status/…

Cal ser sincers. Si fas només un gol, no has jugat tan bé… Si et fan dos gols, no has jugat tan bé… Si et guanyen a casa (o tu perds), no has jugat tan bé… I qui escoltant Gundogan s’ofen, que tanqui la porta al marxar! ♥️…

@Culture_Crit Tallin, Estonia.

@nicalpi Hey @nicalpi would be possible to see a real project using hotwire on the frontend? Thanks!

I’ve been developing in Ruby on Rails for 15 years, and managing full stack Rails teams for 12 years. Front end - and more specifically JavaScript development - has always been a massive pain point. ⌛️Until 2008 * We heavily relied on ERB templates and built-in Rails helpers. * It was a simpler time. * For the ones old enough, they will fondly remember scriptacoulus being the pinnacle of JavaScript development. ❤️2009 - 2016 * We’ve seen gems like ‘jquery-rails’ * Then the introduction of the assets pipeline * Rails UJS bought simpler interactivity to our applications. * CoffeeScript was the ‘productive’ way of writing Javascript for Rails developers. * times were good, but font end developers didn’t like the experience. 💔2016 - 2020 * This is where things went a little bit crazy. * BackboneJS, AngularJS, React, Vue.js were a few of the ever growing set of front end libraries.  * Webpacker introduction in Rails aimed to solve the use of those libraries. But things started to get complex. We started to have disagreement within teams on how things should be done, how should front end developers should be integrated in Ruby on Rails teams etc. 💞 2020 to this day Hotwire and Turbo arrived with a small bang in the wider JS community but a huge explosion in the Ruby/Rails world. These tools were promising going back to a simpler way to write applications where JavaScript was important, but as a sprinkles. This was a return to the promise of Ruby on Rails, being the one developer framework (or small team developer framework). And hell did it deliver! It’s never been more productive to deliver properly interactive applications than with Hotwire/Turbo and their Native counterparts. 👉 So my take is, if you’re a Ruby on Rails developer and you’re not investing a large amount of time mastering those new tools, you’re leaving money and productivity on the table. Smooth and productive backend was sorted years ago, and we’re almost there on the front end side. Have you joined the train on board yet?

The biggest takeaway from Seville’s bike boom? Always think at the network level. To establish it as a viable mobility choice, cycle infrastructure must be treated as a series of connections—like roads or rails—designed with continuity, cohesion, visibility and comfort in mind.

82% des Français souhaitent des rues aux écoles dans leur ville selon @KantarPublicFR. Et cela tombe bien pour les Parisiennes et les Parisiens, on en prévoit 300 d'ici 2026. À l'image de celle rue de la Providence dans le 13e.

@luismejiadev La mejor elección.

@pgasulln Sí, en Backend con Rails me he especializado

Uno de lo principales problemas de buscar trabajos en Linkedin es que el sitio está saturado con los jobs de las agencias y fábricas de software, ya hasta parece spam. Por eso es importante saber buscar las vacantes correctas de acuerdo a tu perfil.

@CaveCoder La personal. Así sumas commits.

Cuando la empresa a la que recién ingresas te pide una cuenta de Github... ¿Le das tu cuenta personal o creas una nueva sólo para esa empresa?