Sérgio Marcelino Profile
Sérgio Marcelino

@SergioFilhow

Followers
99
Following
267
Media
3
Statuses
122

NodeJS lover, Serverless, and Terraform advocate. Head of Engineering at @motiadev

João Pessoa
Joined March 2009
Don't wanna be here? Send us removal request.
@GithubProjects
GitHub Projects Community
1 month
Open-Source unified backend framework that combines API endpoints, background jobs, queues, workflows and AI agents into one system. With built-in observability, state management, and multi-language support, Motia simplifies backend development into a single core primitive.
6
29
165
@SergioFilhow
Sérgio Marcelino
2 months
As of everything, computers were gigantic one day and today we're using them on the palm of our hands, same for backend, it once was a day or even a week to deploy, then we shifted to multiple deployments a day, with Motia that's even simpler!
@motiadev
motia
2 months
Backend needs to be simpler, not complex.
0
1
2
@SergioFilhow
Sérgio Marcelino
3 months
Damn! Motia Framework just got 7,000 stars! And we're just starting! https://t.co/rH94cRxfT5
0
0
1
@motiadev
motia
3 months
🎁 HUGE GIVEAWAY ALERT 🚨 Hello Motia Community 👋 Motia just hit 5,000 GitHub Stars ⭐️ And, here's the GIFT with our new LOOK🎁 To celebrate this, YOU can win 1 of the 5 😎motia😎 hoodies/ caps/ tshirts/ tumblrs! Learn how to win in the comments 👇
26
20
56
@motiadev
motia
3 months
🚀 Motia is trending on GitHub again! We’re absolutely thrilled to see Motia making waves in the developer community. Opensource FTW.
2
3
10
@motiadev
motia
4 months
Look who is trending on GitHub with 3K Stars!
4
3
16
@motiadev
motia
5 months
🎉 Motia v0.2.2 is here! 🔥 Main highlights: ✅ We've introduced the official Motia Manifesto! Read about our vision. ✅ Project creation is now interactive. ✅ Major stability improvements & bug fixes. Better Developer experience, more reliable streaming!
2
4
15
@SergioFilhow
Sérgio Marcelino
4 years
Sometimes going faster is not the smartest move. So the rules doesn’t always apply to being a Senior, totally agree!
@chimon1984
Ryan Edge techhub.social/@chimon 💙
4 years
Senior does not equate to faster. If anything it means more methodical.
0
0
3
@SergioFilhow
Sérgio Marcelino
4 years
@GergelyOrosz We can do both, I always have three types of goals in mind and have regular checkpoints to see where I am at each one. The goals are: short, mid and long-term
2
1
1
@kvlly
Kelly Vaughn
4 years
If you force me to login to unsubscribe from your emails, I will just mark your emails as spam.
42
147
3K
@SergioFilhow
Sérgio Marcelino
4 years
@OCam_l Isso fala muito mais sobre o dev que julgou do que sobre o banco em si. Entrar em um projeto julgando algo como errado sem antes entender o porquê com certeza não é uma atitude de um sênior
0
1
2
@SergioFilhow
Sérgio Marcelino
4 years
Um professor um dia falou em aula algo que nunca esqueço: “Se você gosta de jogar futebol, isso não quer dizer que você vai gostar de construir estádios”
@devnic_
nicolas está pleno
4 years
O cara da minha turma, vai trancar a facul no último ano e começou a faculdade pelo seguinte motivo
0
0
1
@allenholub
Allen Holub. https://linkedIn.com/in/allenholub
4 years
“Complexity sells better” - Edsger Dijkstra Explains a lot.
5
43
220
@svpino
Santiago
4 years
Adding more people to a late project makes it later. This is Brooks Law, and it's based on the increase in communication overhead as more people participate.
24
138
735
@github
GitHub
4 years
Need to add some ASCII art flow diagrams to your README or code comments? YES → https://t.co/U6E3T0t0JY (งツ)ว
23
737
3K
@SergioFilhow
Sérgio Marcelino
4 years
Exactly, do not blame the intern for accidentally deleting a table “without where”. Blame the process that allowed everyone to access production db in first place
@allenholub
Allen Holub. https://linkedIn.com/in/allenholub
4 years
It was a harmless mistake to send a test email, but I’m a little disturbed by the "blame the intern" thing, even if it’s a joke. The problem is never a person, it’s the system. Fix the system.
0
0
1
@allenholub
Allen Holub. https://linkedIn.com/in/allenholub
4 years
The best way to handle the possibility of future changes in your code is to make the code so simple that making those changes is easy. Don’t try to predict the future.
5
46
267
@allenholub
Allen Holub. https://linkedIn.com/in/allenholub
4 years
A programmer’s biggest enemy is unnecessary complexity. Write exactly what you need to write to solve the problem at hand, not one semicolon more.
11
102
415
@allenholub
Allen Holub. https://linkedIn.com/in/allenholub
4 years
Looking at "velocity" is like looking at the tachometer in a car while you have the clutch in. RPM is not an indication of how fast a car is moving, or whether it’s moving at all for that matter.
9
10
83