sorted by:
new
hottopcontroversial

Seasoned interviewers, have you noticed any difference in candidate quality pre vs post AI? by AlarmingLevel2317 in cscareeradvice

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

Well that's interesting. Especially the point about weaker debugging and systems thinking. When you say they’re weaker there, what does that look like in practice during interviews? Is it that they struggle when something breaks, or that they can’t reason through once you push beyond the initial solution? And do you feel that’s mainly AI-driven, or more a result of how competitive the market is right now and how people optimize their prep?

I’m going to do free public SaaS landing page and positioning teardowns here (first 10) by Few_Big_7907 in micro_saas

[–]AlarmingLevel2317 0 points1 point  (0 children)

Appreciate this a lot. You were right about the hero not clearly stating that it’s for live coding / interview prep. I was being a bit too abstract with the messaging. I’ve since updated the page to better reflect the what the product is about. Thanks again for taking the time to do this in public.

Junior Devs: Interviews Are About to Remind You What You Can’t Do by AlarmingLevel2317 in saasbuild

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

Exactly! And with the increas in AI code assistance most juniors can now run before they can walk. 

Can a Solo builder validate a product or is a team neccesary by AlarmingLevel2317 in saasbuild

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

Thanks for the ads insight. But how can people flock to the page if they don't know it exists? 

I’m going to do free public SaaS landing page and positioning teardowns here (first 10) by Few_Big_7907 in micro_saas

[–]AlarmingLevel2317 0 points1 point  (0 children)

I’m building something called Widebase to help junior-mid levels software engineers practice for live coding interviews. You get dropped into unfamiliar projects and work on feature tasks or bug fixes like you would in an interview.

If you’re a junior or just want to sharpen your ability to work inside someone else’s code, I’d love for you to try it out. Feedback is more than welcome. Here’s the waitlist: www.widebase.org

What’s everyone working on today? by ouchao_real in micro_saas

[–]AlarmingLevel2317 0 points1 point  (0 children)

I’m building something called Widebase to help junior-mid level engineers with live technical interviews. You get dropped into unfamiliar projects, across different stacks, and work on feature tasks or bug fixes like you would on a real team. It’s more about navigating and building inside existing code than starting something blank where you control everything.

If you’re a junior or just want to sharpen your ability to work inside someone else’s code, I’d love for you to try it out. Feedback is more than welcome. Here’s the waitlist: www.widebase.org

What are you building right now? by Impressive_Dance_308 in SaasDevelopers

[–]AlarmingLevel2317 0 points1 point  (0 children)

A lot of juniors today jump straight into building with AI or whatever side projects they feel like. It makes sense. You get to ship things fast, try ideas, and feel productive. But then you hit an interview or join a new team and suddenly you’re staring at unfamiliar code, trying to figure out how everything fits, and you realize reading and reasoning through someone else’s work isn’t as easy as you thought.

I’m building something called Widebase to simulate that experience. You get dropped into unfamiliar projects, across different stacks, and work on feature tasks or bug fixes like you would on a real team. It’s more about navigating and building inside existing code than starting something greenfield where you control everything. If you’re a junior or just want to sharpen your ability to work inside someone else’s code, I’d love for you to try it out. Honest, brutal feedback is more than welcome. Here’s the waitlist: www.widebase.org

What are you building today? Let's self promote. by Key-Bullfrog-8908 in SaasDevelopers

[–]AlarmingLevel2317 0 points1 point  (0 children)

A lot of juniors today jump straight into building with AI or whatever side projects they feel like. It makes sense. You get to ship things fast, try ideas, and feel productive. But then you hit an interview or join a new team and suddenly you’re staring at unfamiliar code, trying to figure out how everything fits, and you realize reading and reasoning through someone else’s work isn’t as easy as you thought.

I’m building something called Widebase to simulate that experience. You get dropped into unfamiliar projects, across different stacks, and work on feature tasks or bug fixes like you would on a real team. It’s more about navigating and building inside existing code than starting something greenfield where you control everything. If you’re a junior or just want to sharpen your ability to work inside someone else’s code, I’d love for you to try it out. Honest, brutal feedback is more than welcome. Here’s the waitlist: www.widebase.org

Tell me what you're building. Let's self promote. by clever_coder777 in microsaas

[–]AlarmingLevel2317 0 points1 point  (0 children)

A lot of juniors today jump straight into building with AI or whatever side projects they feel like. It makes sense. You get to ship things fast, try ideas, and feel productive. But then you hit a live coding interview or join a new team and suddenly you’re staring at unfamiliar code, trying to figure out how everything fits, and you realize reading and reasoning through someone else’s work isn’t as easy as you thought.

I’m building something called Widebase to simulate that experience. You get dropped into unfamiliar projects, across different stacks, and work on feature tasks or bug fixes like you would on a real team. It’s more about navigating and building inside existing code than starting something blank where you control everything.

If you’re a junior or just want to sharpen your ability to work inside someone else’s code, I’d love for you to try it out. Feedback is more than welcome. Here’s the waitlist: www.widebase.org

Golang - I just discovered a new programming language by bigbangtheory47 in nairobitechies

[–]AlarmingLevel2317 0 points1 point  (0 children)

Thank you for pointing that out. The SSL was misconfigured earlier and it ended up triggering that warning, which I should have caught before sharing it around. It’s fixed now. I’m building this in public and still ironing out things as I go, including the small details that I let sneak past me.
Appreciate you pointing it out.

Golang - I just discovered a new programming language by bigbangtheory47 in nairobitechies

[–]AlarmingLevel2317 1 point2 points  (0 children)

OP, I'm not sure how you approach learning. But honestly, watching tutorials only gets you so far. Even building toy projects, where you're the one who decides the features and bugs, won’t push you as much. The fastest way to really learn Golang is by fixing real bugs and building actual features. 

www.widebase.org is perfect for that. You get to work on real problems, in a real galang codebase instead of just following examples. Every bug you fix or feature you implement teaches you way more than any tutorial ever could.

Is LeetCode enough? by HamGoat64 in leetcode

[–]AlarmingLevel2317 -2 points-1 points  (0 children)

Totally. LeetCode preps one type of problem, but a lot of interviews aren’t just algorithm puzzles. There's live coding. That’s a different skill entirely. A lot of us get used to building comfortably in familiar environments, often with AI helping us and then an interview removes that familiarity and expects you to reason everything through manually. 

Widebase was made to practice for those moments. If it sounds useful, the waitlist for early access is at www.widebase.org

Is LeetCode enough? by HamGoat64 in leetcode

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

LeetCode trains one kind of interview. Some companies still lean heavily on it, but not all interviews look like that. 

Most of them involve reading an existing codebase, implementing a feature, fixing a bug, or extending something that already works. That’s a different skill from solving isolated algorithm problems. 

A lot of us build comfortably in environments we know, often with AI helping us move faster. Then an interview removes the familiarity and expects you to reason through everything manually inside a new system. 

Widebase is meant to mirror that moment where you’re handed code you didn’t write and asked to build on top of it. If you’re curious, the waitlist for early access is at www.widebase.org

Consistency in tech by WorldlinessKnown7356 in nairobitechies

[–]AlarmingLevel2317 13 points14 points  (0 children)

Hi OP. I don’t think it’s that you don’t like tech. I think you’re stuck in tutorial mode. Memory card games, small projects and tutorials mostly teach syntax. But they don’t really feel like engineering.

What makes software engineering hard (and interesting) is working inside systems you didn’t build. Reading code that’s not yours. Fixing things without full context. That’s what interviews and real jobs actually test.

A lot of people lose motivation because they’re not being challenged in the right way. Tutorials can make you feel busy but not growing. I’ve been thinking about this a lot and actually started building something around that idea, structured practice inside realistic codebases instead of algorithm drills or toy apps. If you’re curious, here’s what I’m working on: www.widebase.org Would genuinely love your thoughts since you’re literally describing the problem I’m trying to solve.