u/TariqKhalaf

 I'm working on a small project and decided to add dark mode as a nice to have. Thought it would be simple. Just flip some background and text colors, maybe adjust a few borders, done. But the more I dig in, the messier it gets. Box shadows that look fine on light mode completely disappear on dark. Hover states that worked well before now feel off. And don't even get me started on form inputs and how different browsers render them.

I caught myself just eyeballing it and calling it good enough. But then I tested with actual dark mode system preferences and realized my contrast ratios were terrible on some components.

So I'm curious. Do you actually write tests for dark mode, or do you just toggle it on manually and scroll through the page a few times? Do you bother with automated visual regression tests for both themes? Or is this just something everyone wings and fixes when a user complains?

I want to do this right without overcomplicating a side project, but I also don't want to ship something that looks broken half the time.

I’m a big fan of finding little pockets of peace on a ship, especially during a sea day when everyone seems to be everywhere at once. On my last cruise, I stumbled onto a forward observation deck that was almost empty while the pool area was packed. It completely changed my day.

Now I’m curious: what are your go-to quiet spots? Could be a certain lounge in the morning, an upper deck at the back, or even a hidden corner of the library. I’d love specific ship names or class types if you have them, since layouts vary so much. Also any tips for checking out these spots without looking like you’re lost? I’m trying to build a little mental map for my next trip, and I think fellow cruisers have the best secrets. Thank you in advance for sharing your hideaways.

Got some feedback from a client yesterday that sounds simple on paper. Just move this section above that one, change the button color to something that pops more, and make the hero image full bleed. But the way the current layout was built with flexbox and some overlapping elements, moving one section means recalculating margins, checking breakpoints, and probably breaking three other things.

I'm not mad at the client. Their requests make sense visually. I'm frustrated that I didn't build it with this level of flexibility from the start. The first version worked fine and looked clean, but now every change feels like surgery.

Do you have a mental checklist for anticipating these kinds of design requests early? Or do you just accept that iteration means refactoring and build that time into your estimates? I'm trying to get better at building components that can be rearranged without pain, but sometimes the final design that gets approved mid project is completely different from the wireframes we started with.

Curious how other devs balance building things the right way versus building things the changeable way.

I'm in the lucky position of having two offers after a long search. But neither feels perfect. Job A pays about 15% more and has great benefits, but the commute is brutal and the culture seems intense. Job B is closer to home, seems more relaxed, but the pay is barely an upgrade from my current role and growth looks limited. I keep going back and forth. I'm worried I'll take the money and burn out, or take the comfort and feel stuck.

For people who've been in this spot, how did you actually decide? Did you make a pros and cons list? Flip a coin? Go with your gut? I'm also curious if you regretted choosing money over balance, or vice versa. I'd love to hear real stories, not just generic advice.

Thanks.

At this point I genuinely believe Excel is the real ERP layer behind most enterprises 😭 Every implementation starts with: 1) “single source of truth” 2) “fully integrated workflows” 3) “real-time visibility”

…and then 18 months later someone in finance has a spreadsheet called FINAL_v2_ACTUAL_USE_THIS_ONE xlsx running half the company.

I used to think this was just a smaller company problem, but even huge ERP environments seem to develop these weird “shadow systems” over time. Usually because: - reporting doesn’t match operational reality anymore, - departments evolve faster than workflows, - approvals get patched temporarily (“temporarily” = 4 years), - nobody wants to touch legacy logic because one wrong change breaks invoicing for an entire region.

The funniest/scariest part is how much tribal knowledge forms around it. “There’s a CSV export you need to run every Thursday, but only after warehouse sync finishes… unless procurement changed the item mapping again.”

At some point the ERP stops being the system and becomes the thing orbiting around spreadsheets. A friend dealing with an ERP described almost the exact same situation. Eventually they brought in additional consulting team mostly because nobody internally understood which workflows were still intentional and which were just leftovers from old operational decisions.

Curious does ANY company fully escape spreadsheet gravity long term? Or is this just the natural final form of enterprise software?

 I have been a marketing coordinator for about three years at a small agency. The work is fine but there is no real room to grow and the pay is stuck. I got an offer for an administrative assistant role at a well known tech company. The pay is actually slightly higher and the benefits are way better. But the title is a step backward.

I worry that future employers will look at my resume and see coordinator down to assistant and assume I could not handle more responsibility. At the same time, getting my foot in the door at this larger company could open up internal moves after a year or so.

For people who have made a similar choice, how did it work out? Did the title matter as much as you thought? Or did the company name and what you actually did there end up being more important?

I am in my early 30s and feel like I should still be moving up, not sideways or down. But the day to day reality of my current job is draining and this new one seems calmer with better people. I would love to hear from anyone who took a seemingly lower title for a better situation and how you explained it later.

I’ve noticed a huge gap between building something that technically works and building something people actually keep using. Most side projects in web dev seem to stall after launch, even when the stack is solid and the UI looks polished

I’m curious what people here think is usually missing. Is it marketing, solving a real problem, consistency, distribution, SEO, networking, or just time?

I’ve shipped a few small apps over the last couple years and the technical side always felt like the easiest part. Authentication, hosting, CI/CD, databases, and even decent frontend UX are more accessible than ever now. But getting repeat users feels like an entirely different skill set that most developer content barely talks about

At the same time, I see a lot of “build in public” advice that seems optimized more for engagement than actual sustainable products.

For anyone who has grown a project beyond a few hundred users, what ended up mattering most in hindsight? And what advice would you ignore if you were starting over today?

Every time localStorage comes up, people say “don’t use it, use IndexedDB, it’s bad,” etc. I get the concerns, but in my case I’m just storing things like a theme preference and a couple of UI flags. No sensitive data, nothing critical. localStorage feels like the simplest option here, but it almost feels like I’m doing something wrong by using it.

Is most of the hate just about people misusing it as a database? Or are there real downsides even for small key/value stuff like this? Also, when would you pick sessionStorage instead?

Curious how people handle this in real projects without overengineering it.

Booking my first cruise (4-night Bahamas) and I’m stuck on the cabin choice. The difference between an interior and a balcony is about $300, which feels like a lot for a short trip.

Part of me thinks I’ll barely be in the room anyway, just to sleep and shower. But at the same time, having a balcony for coffee in the morning or a drink at night sounds really nice. For those who’ve done shorter cruises, did you actually use the balcony much? Or did it end up not being worth it?

Also curious about things like wind, noise, etc. Does it ever make the balcony less usable? Trying to decide if I should save the money or if I’d regret not upgrading.

 I've been doing frontend work for about five years, and the pace of new frameworks, build tools, and libraries is honestly starting to wear me down. Just this month I've seen hype around new meta-frameworks, another state management solution, and yet one more way to do CSS. I try to ignore the noise and stick with what works, but then I worry my skills are becoming irrelevant. How do you decide what's worth learning versus what's just churn? Do you set aside regular time for exploring new tech, or do you only learn on the job when a project demands it? I'm curious about practical strategies from other devs who've been doing this for a while. I don't want to burn out chasing every trend, but I also don't want to get left behind. Would love to hear how you balance staying sharp with keeping your sanity.

I just want to hit some badminton or tennis a couple times a week but everything around here feels either super expensive or completely impossible to book. Ive tried a few places in Irvine and Tustin but half the time their websites are useless or they want you to call during some random two hour window when Im literally at work.I even drove out to a spot in Fountain Valley last week after checking their online schedule and when I got there the guy told me theyve been fully booked for a week for some tournament. thanks for updating your website I guess.I work weird hours so I need something flexible.

does anyone have a go to spot around Santa Ana or Costa Mesa that has decent court time without a crazy membership? Or maybe something near Anaheim? i dont mind driving a bit just need something thats not a total headache every single time lol.also if anyone knows any good drop in games for volleyball or basketball let me know. Trying to stay active but OC makes it weirdly hard sometimes lol .Thanks

My grandmother had this Depression era cake recipe that uses mayonnaise instead of eggs and oil. The first time I made it I was sure it would be disgusting. It turned out to be one of the moistest chocolate cakes I've ever had. No weird taste at all. Just rich and dense.

It got me thinking about other old recipes that use surprising substitutions or combinations that sound wrong on paper but work perfectly. Things like tomato soup cake, vinegar pie, or peanut butter and pickle sandwiches. I've heard of some but never tried them.

I'm not looking for hard times ration recipes necessarily, just anything where the ingredient list makes you do a double take. Bonus if it actually tastes good and not just historically interesting.

Does your family have something like that? Something you grew up eating that other people find strange until they try it? Or a recipe you found in an old community cookbook that uses an ingredient in a way nobody would today.

I'd love to try making a few of these odd sounding classics. Especially desserts or baked goods. The weirder the combo the more curious I get.

Curious how others have navigated this. Over the years I’ve jumped on a few tools/frameworks that felt like “the future” at the time, but ended up adding more complexity than value for my actual projects

For me, it’s usually abstractions that promise cleaner architecture or better scalability, but in practice introduce indirection that makes onboarding harder and debugging slower. Sometimes the ecosystem just wasn’t mature yet, other times I didn’t really need the extra layer at all

I’ve started leaning more toward boring, well-understood solutions unless there’s a clear, immediate benefit. But I still worry about missing out on tools that could genuinely improve workflow if adopted at the right time.

So I’m wondering:
What’s something you adopted early that you later rolled back or stopped using?
Was it the tool itself, or how/when you applied it?
Do you have a personal rule now for deciding when to adopt something new vs sticking with the basics?

Would be interesting to hear both frontend and backend perspectives here.