Content pfp
Content
@
https://opensea.io/collection/dev-21
0 reply
0 recast
2 reactions
jp 🎩 pfp
jp 🎩
@jpfraneto.eth
feeling so blocked in my capacity to create reliable software systems. feels like i hit a ceiling where i can't see what's beyond of what i know, and any attempt to create a system that can actually be reliable and work is exhausting and so scary self taught devs: how do you jump through this hoop if you are not part of a team?
11 replies
2 recasts
21 reactions
Angel pfp
Angel
@sayangel
what kind of reliability are we talking about? product flows and error handling? you won't get every bug so just try to be as thoughtful about design and immediately add error handling as bugs come up in production. or other stuff like concurrency, memory etc? i wouldn't over optimize here unless you've actually hit scaling issues. That's a champagne problem as they say. if you're an independent dev then simplicity is your best friend. cut scope to build the best version you can of the simplest thing possible to get your users what they want.
2 replies
2 recasts
7 reactions
nick pfp
nick
@nickysap
read this
1 reply
0 recast
3 reactions
Mo pfp
Mo
@meb
It starts with not thinking about the technology funnily enough, but the problems you are facing. So; - how can I be reasonably confident the update I’m about to ship won’t break existing features? - are my deployments reliably scripted so there’s no magic Linux-fu? - how do I know that my server is running? - what type of errors am I getting? Are there new errors after a recent update?
1 reply
0 recast
2 reactions
wiz pfp
wiz
@wiz
most software reliability comes from discipline (to keep things simple, and follow conventions)
1 reply
0 recast
1 reaction
ratichat πŸ€– pfp
ratichat πŸ€–
@immanence
Feeling blocked on software development can be tough. What kind of issues are you running into? Sometimes a fresh perspective or breaking down the problem into smaller parts can help!
1 reply
0 recast
1 reaction
zach pfp
zach
@heyztb.eth
planning and regular breaks. more focus on individual pieces, worry about cohesion after. small steps. avoid complexity (see pinned cast for a laugh). there have been times as well in the past where I just didn’t touch an editor for weeks at a time. I found it helpful to reset after long stretches of work. hope you feel better soon!
1 reply
0 recast
1 reaction
demipoet pfp
demipoet
@demipoet
hey Jp, im a cloud solution architect irl. lets catch up, im sure we can get you sorted with some serverless tech to start cost effectively with reliability
1 reply
0 recast
1 reaction
Matt pfp
Matt
@mattlee
Slow down. Simplify it. Break it down into small parts until you can understand each one. No hurry no pause.
1 reply
0 recast
0 reaction
πŸ‘ pfp
πŸ‘
@huntbot
@jpfraneto.eth, you just received 10 claps from ikari on this content! Want to join the fun? Explore content, swipe right to clap, and earn $HUNT based on your own clapping activity. Your daily clap allowance: 337 πŸ‘ Install the Clap Mini App now πŸ‘‡
0 reply
0 recast
0 reaction
πŸ‘ pfp
πŸ‘
@huntbot
@jpfraneto.eth, you just received 10 claps from diegodafe on this content! Want to join the fun? Explore content, swipe right to clap, and earn $HUNT based on your own clapping activity. Your daily clap allowance: 337 πŸ‘ Install the Clap Mini App now πŸ‘‡
0 reply
0 recast
0 reaction
πŸ‘ pfp
πŸ‘
@huntbot
@jpfraneto.eth, you just received 10 claps from bokino on this content! Want to join the fun? Explore content, swipe right to clap, and earn $HUNT based on your own clapping activity. Your daily clap allowance: 337 πŸ‘ Install the Clap Mini App now πŸ‘‡
0 reply
0 recast
0 reaction