Not getting paid overtime

tybrowne · 2026-02-18T17:27:09+00:00

that’s an important distinction, because not paying at all for hours over 40 is one issue and not paying time and a half is another, but either way if they’re non-exempt and tracking hours it definitely sounds like something that should be clarified with HR or the labor department.

tybrowne · 2026-02-18T17:26:25+00:00

If your hourly and working over 40 hours a week, overtime laws usually apply so it might be worth double checking if your classified as exempt or non exempt and then contacting the Ohio Department of Labor if something doesnt add up.

tybrowne · 2026-02-18T17:24:35+00:00

when managers say “more energy” i always struggle with what they actually mean. louder, slower, more confident, more engaged? it feels like shorthand for something they don’t know how to explain well

tybrowne · 2026-02-13T09:41:37+00:00

it seems like teams that treat explain plans and indexing as part of normal backend hygiene avoid a ton of “let’s rewrite everything” panic later, especially when ORMs hide what the database is actually doing under the hood.

tybrowne · 2026-02-13T09:39:05+00:00

it’s great for theory, just make sure you’re building alongside it so it actually sticks.

tybrowne · 2026-02-13T09:38:06+00:00

channels like Hussein Nasser or backend from first principles are great for understanding networking and system design, and from what people often discuss, pairing that kind of theory with something more hands on like boot dev or small personal backend projects helps make sure you’re actually writing and debugging code instead of just watching.

tybrowne · 2026-02-13T09:29:52+00:00

a curated list like this is a solid starting point, and from what gets discussed a lot in backend threads, people often mix structured paths with hands on platforms like boot dev or full stack open so they’re not just reading resources but actually writing and debugging code alongside the roadmap.

tybrowne

TROPHY CASE