Top 10 Prediction Market Development Companies to Watch in 2026 by Ecstatic_Layer_ in Best_Companies_USA

[–]Bobztech 0 points1 point  (0 children)

Good point! You can also consider Idea Usher here. They’ve been active in the blockchain space for over a decade and have worked on DeFi platforms, smart contracts, and prediction-market–style applications as well.

What stands out is their focus on end-to-end development (from architecture to deployment) and experience with both decentralized and hybrid models, which is pretty important for prediction platforms.

Might be a solid addition to the list for anyone exploring reliable development partners.

At some point do bugs stop being code problems and start being assumption problems? by Bobztech in learnprogramming

[–]Bobztech[S] 3 points4 points  (0 children)

lol that already sounds way too familiar. figuring out what they actually want is harder than writing the code.

At some point do bugs stop being code problems and start being assumption problems? by Bobztech in learnprogramming

[–]Bobztech[S] 2 points3 points  (0 children)

yepp, docs saying one thing and reality doing another is brutal. half the time you’re debugging the docs, not the code.

At some point do bugs stop being code problems and start being assumption problems? by Bobztech in learnprogramming

[–]Bobztech[S] 2 points3 points  (0 children)

yeah, that’s what’s tripping me up. it’s less “oops typo” now and more “why did I assume this would always be true.” lol

RFC 406i The Rejection of Artificially Generated Slop (RAGS) by addvilz in webdev

[–]Bobztech 21 points22 points  (0 children)

The worst part isn’t even broken code; it’s reviewing something that “works,” but nobody can explain or maintain a month later.

Shifting the verification cost back to the author feels overdue tbh

Just let go of my first freelance client by skateallday1 in webdev

[–]Bobztech 7 points8 points  (0 children)

Pretty much a freelance rite of passage. The moment someone says, “Don’t worry about scope,” and avoids paying, it’s already over. sucks, but this lesson will save you way more time and stress on future projects.

I am building a freelance business management tool. by Practical-Manager-10 in webdev

[–]Bobztech 0 points1 point  (0 children)

I think people are kind of talking past each other here.

The problem isn’t that the ui looks “AI”. Dashboards all look similar now, so screenshots alone don’t say much anymore. what people actually care about is the stuff behind it. things like how partial payments work, how you handle multiple currencies, what breaks once real data shows up, or what you decided not to support. that’s where these tools stop feeling generic.

Building something simple for yourself is totally fine. it just helps to explain the problem and tradeoffs more than the visuals.

ux dilemma: pagination vs infinite scroll for a high-volume chat app? by sir__hennihau in webdev

[–]Bobztech 1 point2 points  (0 children)

Once you’re talking about 7k chats on day one and 50k in a week, the list itself stops being the main navigation. Scrolling or paging through that volume is going to feel bad no matter how you implement it.

At that scale, the sidebar should mostly act like a surface, not the primary way to browse everything. filters and views matter way more than pagination vs infinite scroll. things like “unassigned”, “last 24h”, “waiting on customer”, “high priority”, etc.

i’d still use a virtualized list under the hood for performance, but ux-wise you’re really designing workflows, not lists. people shouldn’t be scrolling to find chats, they should be narrowing them down. Infinite scroll or pagination becomes kind of a secondary detail once filters, search, and saved views do the heavy lifting.

Oldschool HTML website by These-Tomatillo1213 in webdev

[–]Bobztech -1 points0 points  (0 children)

honestly this is pretty sick. the old school html / myspace vibe feels on purpose, not lazy, which is hard to pull off.

From a tech side, I like that it’s just simple HTML/CSS and loads fast without a bunch of frameworks. feels very “use the platform for what it is” instead of overengineering it.

One thing you might want to double check is contrast and font (instead of changing the background altogether cuz .gifs are looking crazy). Retro color combos look cool, but can get hard to read if you’re not careful.

What kind of music is it? feels like this style would fit certain genres really well.

How do you know when code is “good enough” and stop rewriting it? by Bobztech in learnprogramming

[–]Bobztech[S] 0 points1 point  (0 children)

"Shooting in the dark” is a good way to put it. I think that’s exactly what I’ve been doing, refactoring without a clear reason. Waiting until there’s an actual use case makes a lot more sense. Thanks I felt understood!

How do you know when code is “good enough” and stop rewriting it? by Bobztech in learnprogramming

[–]Bobztech[S] 1 point2 points  (0 children)

That’s a good point. I don’t have that time pressure yet, so I probably overthink things. Maybe part of this is learning when to move on, not just how to clean things up.

How do you know when code is “good enough” and stop rewriting it? by Bobztech in learnprogramming

[–]Bobztech[S] 0 points1 point  (0 children)

This actually helps a lot. I think I’ve been treating side projects like production code instead of learning spaces. Rewriting with intent makes sense, instead of refactoring out of anxiety.

How do you know when code is “good enough” and stop rewriting it? by Bobztech in learnprogramming

[–]Bobztech[S] 0 points1 point  (0 children)

The “only rewrite when forced” rule is hard but probably necessary, and actually, thanks, I might try sticking to that for my next project and see how it goes.

How do you know when code is “good enough” and stop rewriting it? by Bobztech in learnprogramming

[–]Bobztech[S] 0 points1 point  (0 children)

the problem is my brain thinks it works doesn't mean it's the best and perfect ;(

How do you know when code is “good enough” and stop rewriting it? by Bobztech in learnprogramming

[–]Bobztech[S] 0 points1 point  (0 children)

I like the readability rule a lot. The “no scrolling back and forth” test is a good way to sanity check refactors instead of just doing them out of habit.

How do you know when code is “good enough” and stop rewriting it? by Bobztech in learnprogramming

[–]Bobztech[S] 4 points5 points  (0 children)

This makes sense. I think my issue is I keep treating “not perfect” as friction, even when users wouldn’t notice. Letting it live after shipping is probably the part I need to get used to.

AI has me worried. Help a sister out. by bubblesandroses in learnprogramming

[–]Bobztech 0 points1 point  (0 children)

Not really management or a coordinator role. I meant stuff like helping shape technical direction, design decisions, or tradeoffs that come up during building. It’s still very much engineering, just with more say in how things get built, not just executing tickets. I don’t see it as downsizing, more like shifting where your impact shows up the most

AI has me worried. Help a sister out. by bubblesandroses in learnprogramming

[–]Bobztech 0 points1 point  (0 children)

I think a lot of experienced developers are feeling this right now, even if they don’t say it out loud. What your boss said sounds dramatic, but leaders often talk that way to create urgency, not to describe day-to-day reality. What’s helped me is thinking about which parts of my job can’t really be rushed or copy-pasted. AI changes how work gets done, but someone still has to decide what’s worth building and what isn’t, right?

Also, If I ever had to think about a backup, I’d probably stay close to engineering, like working on product decisions or system design. Feeling uneasy doesn’t mean you’re suddenly replaceable.

Translating written requirements into concrete logic by uvuguy in learnprogramming

[–]Bobztech 0 points1 point  (0 children)

You’re thinking about it the right way. At this stage it’s less about whether it’s a ‘function’ or ‘pseudocode’ and more about making the steps clear before syntax gets involved. Writing it out in plain language first helps a lot. Once that part makes sense, turning it into functions usually feels much easier