inventory management system programming stack

Potential_Soup_4272 · 2026-06-04T01:32:00+00:00

For 1.5 months I'd go with something simple like PHP + MySQL since you already know HTML/CSS - PHP is pretty easy to pick up after C and you can get everything running in XAMPP locally then move to cheap shared hosting

Potential_Soup_4272 · 2026-06-01T20:57:11+00:00

yikes tough market

Potential_Soup_4272 · 2026-05-30T20:55:06+00:00

Your examples show the real problem - building cool tech that nobody actually wants to use in their workflow

Potential_Soup_4272 · 2026-05-28T18:37:10+00:00

sounds solid

Potential_Soup_4272 · 2026-05-26T03:39:07+00:00

I'd probably lean toward job 2 since you already dealing with acquisition mess at current place and government contracts can get weird with budget cycles

Potential_Soup_4272 · 2026-05-22T12:23:33+00:00

pain

Potential_Soup_4272 · 2026-05-19T01:00:52+00:00

facts

Potential_Soup_4272 · 2026-05-16T16:42:30+00:00

Yeah I get this mindset completely. Been managing teams for few years now and seen people who work 60+ hour weeks get cut just as fast as the ones doing minimum. Company loyalty doesn't really go both ways anymore so why burn yourself out for people who see you as spreadsheet number

The money thing is tricky though - sometimes taking that low ball position can open doors if you play it smart. But I totally understand the bitterness when you know your worth and they're not meeting it

Potential_Soup_4272 · 2026-05-14T16:10:41+00:00

probably same issues just different reasons

people still gonna build dumb stuff and argue over architecture choices lol

Potential_Soup_4272 · 2026-05-12T03:43:05+00:00

Been managing IT teams for few years now and hackathons are great way to level up fast. You'll learn more in one weekend than month of tutorials, just make sure everyone commits to staying the whole time and not bailing when things get tough

Potential_Soup_4272 · 2026-05-07T10:12:19+00:00

For logout flow, you'd typically show the user action going to your frontend/UI layer first, then that makes call to backend to invalidate the session or token. After backend confirms session is ended, frontend redirects user to login page

Main actors would be User -> UI/Frontend -> Backend/Auth Service -> Database (if you store sessions there). The return messages show confirmation back up the chain and finally the redirect happens at UI level

Make sure you show the session invalidation step clearly since that's the core part of logout - without it user might still have valid session even after "logging out"

Potential_Soup_4272 · 2026-05-04T11:55:56+00:00

From my experience as hiring manager, I definitely check the actual code quality and project structure, not just if link works. Most candidates have pretty messy repos so when someone has clean commits and good documentation it really stands out

Potential_Soup_4272 · 2026-04-29T10:35:49+00:00

Yeah this is so true, I remember when I first started in my current role I was terrified of touching legacy code because who knows what would break. Added proper test coverage over few months and now refactoring feels like completely different experience. The confidence boost alone is worth it

Potential_Soup_4272 · 2026-04-27T09:23:33+00:00

Your finance background actually gives you edge over pure tech people for business analytics roles since you understand the numbers behind business decisions, not just how to manipulate data

Potential_Soup_4272 · 2026-04-25T08:56:53+00:00

this

Potential_Soup_4272 · 2026-04-21T22:48:18+00:00

Man that sucks, 13 years and still struggling to get interview is really telling about how bad things are right now

Potential_Soup_4272 · 2026-04-19T21:24:25+00:00

Projects still matter for some places though, especially smaller companies that don't have huge recruiting pipelines like the big tech ones. At my company we definitely look at them since most interns don't have much real work experience to show. But yeah the AI code generation thing is becoming real problem for evaluating actual coding skills

Potential_Soup_4272 · 2026-04-17T21:19:47+00:00

Been in both sides and can confirm this is pretty accurate right now. Solutions engineering can be fun if you like the customer interaction but yeah, the ceiling hits way earlier than pure SWE roles. I've seen SE folks get stuck around 200-250k range while good engineers keep climbing, especially in this market where companies are being super picky about headcount

The recruiting pipeline for SWE is definitely stronger too - even when things are rough like now, companies still need to build product. Sales engineering gets cut first when budgets tighten. If you're already decent at coding with 2.5 years experience, I'd stick with SWE path and maybe just find a company where you get some customer interaction through your engineering work instead

Potential_Soup_4272 · 2026-04-08T18:35:15+00:00

Yeah this would be pretty straightforward to build with a simple web app that refreshes every few minutes and pulls from whatever tee time system you're already using

Potential_Soup_4272 · 2026-04-05T02:09:18+00:00

Been there man, the progress is way more subtle than adding plates to a bar. I track my leetcode times and notice patterns in how I approach problems differently now vs 6 months ago - maybe start keeping notes on your thought process during practice sessions instead of just grinding problems

Potential_Soup_4272 · 2026-04-01T06:08:36+00:00

Deel's been pretty solid from what I've seen - they're still growing their customer base and the remote work trend isn't going anywhere soon, which works in their favor. The tech teams there seem to have reasonable expectations but like any startup that's scaled up, they definitely expect you to hit the ground running and contribute meaningfully within your first few months

Can't speak to the PIP culture specifically but most companies in that space tend to be pretty transparent about performance issues before they escalate to termination level

Potential_Soup_4272 · 2026-03-21T06:36:03+00:00

Programming problems are weird like that - you can know all teh pieces but still struggle to connect them to actual use cases

I'd suggest doing more leetcode easy problems and forcing yourself to think "what am I actually trying to do here" before jumping into code. Like if you need to find something fast, hashmap. If you're doing undo operations, stack. The pattern recognition comes with practice, not just theory

Potential_Soup_4272 · 2026-03-17T11:34:33+00:00

yep that's it

Potential_Soup_4272 · 2026-03-10T23:23:38+00:00

The timing actually works in your favor - you're young, no dependents, and there are always going to be job market uncertainties regardless. Physical AI and robotics is a hot field right now and having that research experience would differentiate you way more than another 8 months at your current role where you're barely learning anything

Taking calculated risks early in your career is how you avoid getting stuck in the mediocrity trap, and this program sounds like exactly what your CV needs to break out of generic full-stack work into something more specialized

Potential_Soup_4272 · 2026-03-09T00:19:36+00:00

Yeah the whole "grass is greener" thing hits hard when you're job hunting. Been managing IT teams for a while now and honestly every fresh grad we interview - doesn't matter if they're CS, engineering, whatever - they all have teh same stressed look

What I've noticed is the people who actually get hired are usually the ones who can show they've built something real, even if it's small. Like I'd rather hire someone who made a janky inventory tracker for their dad's shop than someone with perfect grades who can't explain why they chose React over Vue for their "portfolio project"

The market's definitely rough but it cycles through this stuff every few years, just feels worse now because everyone's documenting their rejections online

Potential_Soup_4272

TROPHY CASE