HN user

masylum

408 karma
Posts30
Comments46
View on HN
handinger.com 2mo ago

Automate shitty tasks with dog agents

masylum
6pts0
paoramen.fika.bar 4mo ago

The Singularity Will Not Be Streamed

masylum
1pts0
paoramen.fika.bar 5mo ago

Hedonism and Entrepreneurship in Barcelona

masylum
2pts2
paoramen.fika.bar 5mo ago

I left my own startup to not become my father

masylum
5pts2
fika.bar 8mo ago

The Talent machine: A predictable recruiting playbook for technical roles

masylum
1pts0
fika.bar 10mo ago

Can It Run Doom?

masylum
1pts0
fika.bar 11mo ago

AI Is Eating the Internet

masylum
4pts2
fika.bar 1y ago

How to build a game without spending euros and hours

masylum
4pts1
fika.bar 1y ago

Show me your calendar. A story, and a management prompt

masylum
1pts0
indie-crafters.com 1y ago

An alternative to the Indie Hacker movement

masylum
3pts0
handinger.com 1y ago

Show HN: Handinger – API to extract data from the Internet

masylum
4pts3
fika.bar 1y ago

All websites look the same: Let's bring the colors back

masylum
4pts0
fika.bar 1y ago

Fear of over-engineering has killed engineering altogether

masylum
98pts79
fika.bar 1y ago

Building Fika: Constraints and Architecture

masylum
2pts0
jsr.io 2y ago

Cheer-reader a cheerio port of readability.js

masylum
1pts1
medium.com 8y ago

Skepticism in an age of polarization

masylum
1pts0
github.com 9y ago

Show HN: Mobx-rest

masylum
7pts0
redbooth.com 11y ago

Show HN: We just open sourced our Scrum planning poker cards

masylum
20pts4
redbooth.com 11y ago

The hamburger menu is definitely bad for your app

masylum
13pts0
redbooth.com 11y ago

Redefine CTO

masylum
1pts0
redbooth.com 11y ago

Dry with Ruby metaprogramming

masylum
5pts2
redbooth.com 11y ago

RSpec testing guidelines

masylum
14pts1
github.com 13y ago

Just open sourced the backbone.middleware module we've been using at Teambox

masylum
3pts0
pau.calepin.co 14y ago

Learning Haskell: Functions

masylum
4pts0
github.com 14y ago

Backbone.Rel: Backbone lightweight model relationship manager

masylum
48pts4
pau.calepin.co 14y ago

Learning Haskell: Algebraic data types

masylum
4pts0
pau.calepin.co 14y ago

Backbone: Dealing with stateful applications (part 2)

masylum
7pts1
pau.calepin.co 14y ago

Backbone: Dealing with stateful applications (part 1)

masylum
110pts20
pau.calepin.co 14y ago

Being recruited in the USA

masylum
165pts146
github.com 15y ago

Brainfuck on Rails

masylum
2pts0

The last two decades of the Internet have been an age of abundance. Creators, advertisers, and consumers benefited from a balance of incentives and a mostly open web. Now, with the rise of consumer AI, that balance is breaking. I explore what comes next in my latest essay.

Hey, this is Pao, the guy building https://fika.bar.

Fika is a place to save, discover and share content built upon 3 products:

- A local-first bookmark manager (Works 100% offline) - A feed reader: With feed discovery from your bookmarks. - A blog/newsletter platform

The only thing it currently does not have is e-reader integration yet. But you get the other 2 products bundled together which make a lot of sense.

What do cellular automata, chaos theory, and Mahjong have in common? In this post, I break down how I built Whatajong: a game created in under 200 hours with zero budget—by tapping into the power of emergence. If you're curious how simple rules can create deep, addictive gameplay, read on.

The point is that "a prop changed" can't be reasoned within a component. If I receive an object as a prop, I can only reason if that pointer in memory will be the same, not wether it has changed. The allocation can happen up in the component hierarchy making this a subtle for even the most senior developers.

Maybe I expressed it incorrectly. When the code is incorrect, it fails in the future. So the user will notice it. This happens when your code relies on some context to work (for instance, if it relies on how the data structure was allocated somewhere up the component hierarchy). When the context changes, then that piece of code starts failing, therefore impacting users.

I agree, but the problem is that when you refer an object inside a hook, the eslint exhaustive deps will tell you to add that object as a dependency. In that example, it's easily solved with destructuring `const teamId = params`, but a lot of developers will blindly follow the eslint complaint.

Redbooth is looking for senior Rails developers.

Join one of the best teams in town and have an impact to the thousands of customers that are using our product.

We are looking for people that have production experience with high traffic websites and are able to learn new technologies. Finding solutions out of the comfort zone is part of our daily routine.

The challenges you will face will be to keep the fast-paced development cycle without sacrificing quality, stability nor performance. To achieve that we successfully architected the application moving away from the classic monolithic default Rails approach.

Our stack includes: Ruby/Rails, Rspec, MySQL, Redis, Erlang/Ejabberd, Javascript/Backbone/Marionette, Travis, Nodejs, Puppet, AWS...

The conditions are exceptional (really good salary and stock!) and we have a strong culture of collaboration and quality work. One example can be our cleaning fridays: developers dedicate time to reduce technical debt, improve tooling and testing coverage.

If you want to grow and be part of one of the most successful startups in Barcelona don't hesitate to apply!

What should I do?

Contact us at jobs@redbooth.com :)