STx

1.2K posts

STx

STx

@stxcode

software engineer, node, typescript, golang react n more 🤘

United States 가입일 Haziran 2024
288 팔로잉59 팔로워
고정된 트윗
STx
STx@stxcode·
1/ 🐦 This long weekend, I redefined and simplified my open source project: “Krow”. 🚀 Krow is a file-based command line REST client. Perfect for developers looking for a lightweight solution. 🌟 #OpenSource #CLI #DevTools github.com/st-osi/krow
English
2
3
4
329
STx
STx@stxcode·
@0xphxdev Thanks, i hope you will try it and give feedback on it. I really like it to use when you are coding in remote environments like coder, you don’t need apps like postman or bruno
English
1
0
1
10
STx
STx@stxcode·
1/ 🐦 This long weekend, I redefined and simplified my open source project: “Krow”. 🚀 Krow is a file-based command line REST client. Perfect for developers looking for a lightweight solution. 🌟 #OpenSource #CLI #DevTools github.com/st-osi/krow
English
2
3
4
329
Phoenix.dev
Phoenix.dev@0xphxdev·
@stxcode What is KROW mainly? Is it a backend framework built on the Go language? Is it one of your projects?
English
2
0
1
11
STx
STx@stxcode·
@unkonfined Just checking no of followers now 🤮
English
0
0
0
2
Unkonfined
Unkonfined@unkonfined·
Stop chasing followers and start engaging.
English
778
187
1K
38K
STx
STx@stxcode·
@csaba_kissi Idk how we define vibe coders here but 100% agree if vibers doesn’t know coding at all
English
1
0
1
33
Csaba Kissi
Csaba Kissi@csaba_kissi·
Unpopular opinion: Vibe coders cannot fully leverage the power of AI for coding.
English
31
1
58
2.5K
STx
STx@stxcode·
@0xphxdev You want to be SOLID huh 🤔 jk great tip though
English
1
0
0
12
Phoenix.dev
Phoenix.dev@0xphxdev·
Your code becomes unmaintainable because one class does everything. This breaks fast when requirements change. That’s a Single Responsibility violation. Fix: Split logic by purpose: • validation • business logic • data access Change becomes isolated. Bugs become easier to trace.
English
1
0
3
29
Phoenix.dev
Phoenix.dev@0xphxdev·
Your service depends on concrete classes. Now you can’t test or swap implementations. That’s a Dependency Inversion problem. Fix: Depend on abstractions. Bad: UserService → MySQLRepo Good: UserService → IUserRepo Now you can: • mock easily • switch DB • scale safely
English
1
0
0
31
STx
STx@stxcode·
What a way to start a day 😀 good morning 🌞☀️
STx tweet media
English
1
0
3
24
STx
STx@stxcode·
@0xphxdev Or strick typing for process.env
English
0
0
1
22
Phoenix.dev
Phoenix.dev@0xphxdev·
This typo broke my entire test environment. And JS didn’t even complain 👇
Phoenix.dev tweet media
English
3
1
17
139
STx
STx@stxcode·
@0xphxdev Spellcheck plugin might help
English
1
0
1
23
Harminder Virk
Harminder Virk@AmanVirk1·
Are we (JS devs) using Admin panels? Laravel has Nova. Rails has Active Admin. Django ships one out of the box. What do we have 👀 Genuinely curious what everyone is using, or if this just isn't a thing in the JS world.
English
36
2
87
24.8K
STx
STx@stxcode·
@justbyte_ Believe me theory matters
English
0
0
0
10
Aryan
Aryan@justbyte_·
Why do colleges prioritize theory over hands-on project building?
Aryan tweet media
English
34
5
119
3.7K
STx
STx@stxcode·
@CodeByNZ This is FE for BE engineers
English
0
0
0
76
NZ ☄️
NZ ☄️@CodeByNZ·
Do backend devs really find joy in doing this ?
NZ ☄️ tweet media
English
448
71
2.9K
405.5K
Phoenix.dev
Phoenix.dev@0xphxdev·
As a developer, have you ever wondered: Upon entering a 16-digit card number, the form immediately indicates that the card number is invalid. There are billions of possible numbers. How the hell is that check that fast? #devthought
Phoenix.dev tweet media
English
3
1
14
128
STx
STx@stxcode·
@jherr @Netlify Wow congratulations Jack keep inspiring 🎉🎉
English
0
0
3
65
STx
STx@stxcode·
@mjackson 💯 work gives peace ☮️ if you love it
English
0
0
0
75
MJ
MJ@mjackson·
If you want to be happy: work.
English
9
4
50
3K
STx
STx@stxcode·
@0xphxdev Also checkout Promise.allSettled
English
1
0
1
13
Phoenix.dev
Phoenix.dev@0xphxdev·
Your UI loads in 3 seconds. Because your API calls run in sequence. Cause: You fetch inside components step-by-step. user → posts → comments That’s a waterfall. Fix: • fetch in parallel • move data fetching to a single layer Bad: await getUser() await getPosts() await getComments() Better: await Promise.all([user, posts, comments]) Frontend performance is mostly data orchestration.
Phoenix.dev tweet media
English
1
1
9
111