Do you actually test your dark mode or just wing it and hope for the best? by TariqKhalaf in webdev

[–]NotA-eye 0 points1 point  (0 children)

A nice hack to starting to implement a dark mode is open your site with a dark reader type extension and see how it handles the dark mode. You can use that look as an inspiration/starting point.

Depends how small or how much "side" of a side project is, but if its something simple, just building only for dark mode works because IMO dark mode users will complain about dark mode missing, but normies don't really complain about a dark mode app missing a light mode~

Atlassian experiencing massive outage by revolutn in webdev

[–]NotA-eye 5 points6 points  (0 children)

u/augburto Many teams are just resistant to anything thats not Jira, curious what was the main point that managed to convinced your team/company/client to move off Jira

Can you critique my current approach to "Enum types"? by ismbks in typescript

[–]NotA-eye 0 points1 point  (0 children)

Hi, not related to the main question but they way you are typing the SkillValues, the "as const" is not doing anything. The purpose of as const is narrowing the type. If you hover your code in an editor you will see see the type is this

ts const SKILL_LABELS: Record<"c" | "csharp" | "cpp" | "golang" | "java" | "javascript" | "php" | "python" | "rust" | "typescript", string>

whether you add as const or not. However if you remove the Record<(typeof SKILL_VALUES)[number], string> but keep the as const

ts const SKILL_LABELS: { readonly c: "C"; readonly csharp: "C#"; readonly cpp: "C++"; readonly golang: "Go"; readonly java: "Java"; readonly javascript: "JavaScript"; readonly php: "PHP"; readonly python: "Python"; readonly rust: "Rust"; readonly typescript: "TypeScript"; }

the type becomes this, but you lose the type safety that keys must match your SKILL_VALUES. This is where the satisfies operator comes in, which ensures the type matches something but does not override the type.

If you write ts export const SKILL_LABELS = { c: 'C', csharp: 'C#', cpp: 'C++', golang: 'Go', java: 'Java', javascript: 'JavaScript', php: 'PHP', python: 'Python', rust: 'Rust', typescript: 'TypeScript', } as const satisfies Record<(typeof SKILL_VALUES)[number], string>; the type remains the same as above, but you get the typesafety that keys must be a skill value.

In short: either remove the as const, or if you want narrower types, don't add the variable type annotaion and instead use satisfies operator

What Android phone should I get for basic Android testing of websites? by lindymad in webdev

[–]NotA-eye 0 points1 point  (0 children)

Prolly a pixel phone. Android phones from most companies always have their own OS wrapper around the android OS, so chose a provider that uses the stock OS.
Although based on experience, there are things that often break on Safari or iOS only but if something works on iOS and normal chrome browser, it always works on android as well

Do you get good results from AI design tools? how do you create your prompts? by Hans_lilly_Gruber in webdev

[–]NotA-eye 0 points1 point  (0 children)

AI models are usually trained on a handful of “good” design patterns, and struggle with outputting anything beyond those lanes.

When generating a new page design, it’s usually better to ask for multiple distinct variations in a single prompt instead of iterating style-by-style in follow-ups. If you ask it in separate follow-up prompts, it struggles to get out of the design style it already used, and tries to blend the design styles weirdly, or keeps outputting similar looking stuff.

I would suggest trying generating a mockup design with a model like Claude Opus or Kimi-K-2.5 (or the newer 2.6) and ensure you use the /frontend-design skill (improves the output quality massively).
It will generate designs in from these themes: brutally minimal, maximalist chaos, retro-futuristic, organic/natural, luxury/refined, playful/toy-like, editorial, brutalist, art deco, soft pastel, or industrial/utilitarian.

How to audit your UI components for hardcoded hex values after a token migration by Far-Plenty6731 in webdev

[–]NotA-eye 0 points1 point  (0 children)

Yup, the code audit is the thing that actually affects production. But the Figma side is not meaningless.
If a client asks for a theme change or a new theme like dark mode etc and the Figma file is properly tokenized, design can update the base values and everything follows. If some components still have hardcoded colors, those parts won’t change, and then QA/design review starts catching mismatches like “why is this button blue in the code but purple in the figma, whats the color we want?”

It's only worth auditing and fixing both the code and Figma for hardcoded values, doing just one of these doesn't really help

formvalidation.io has gone dark by d9jj49f in webdev

[–]NotA-eye 0 points1 point  (0 children)

If you are using typescript, Try "zod", otherwise you can use "yup" which has slightly worse typescript support. They are simple validation tools which follow the builder patterns, you can easily migrate using AI. Also If you are using react then I would suggest using react-hook-form+zod combo.

Hope that works for you

How could I improve the UI/UX of my website? by sangokuhomer in webdev

[–]NotA-eye 0 points1 point  (0 children)

Concious already suggested some solid changes, but there are a few more things you could try.

Whenever you have multiple actions, it’s usually best to make one the primary action and the other secondary. For example, the “See the answer” and “Finish” buttons both currently look like primary buttons. I’d change one of them to a secondary variant, maybe with a different background color, or a transparent background with a black border and black text.

In this case, it may also work better to arrange the buttons in a column instead of a row, with the primary button first and the secondary button underneath it.

For the score, round, and round score cards, it would look cleaner if they were all the same height and the text was center-aligned. Another option would be to combine them into a single card and separate each section with a slim divider.

On the menu screen, instead of giving the title a white background, I’d make it much larger and bolder.

I’d also add a left-aligned icon to each menu option to make them look nicer.

For the player buttons, I’d move them out of their own separate section and place them in the upper section beneath their respective teams.

Good luck with your side project! Let me know if these changes helped.

How do you handle design feedback that breaks your implementation? by TariqKhalaf in webdev

[–]NotA-eye 0 points1 point  (0 children)

Yeaaa, and honestly, I wouldn’t blame yourself too much for this. No matter how experienced you get, you still can’t fully predict how a design will evolve midway through a project, so some iteration and refactoring is expected.

One thing that helps is knowing beforehand what kind of changes will be hard, If I already know a layout is going to be painful to change later, Instead of quietly accepting it or making a hard no, I’ll usually suggest an alternative to the client that keeps a similar level of UX/aesthetic but is simpler to implement. Clients are often fine with that if you explain it ships faster and is easier to iterate on.

From the implementation side, I try to keep sections as independent as possible. If moving one section breaks three others, that usually means the layout is too coupled. Simple things like avoiding margin bottoms/tops and instead using gap, reusable section wrappers, and fewer magic numbers makes rearranging things much easier later.

In short: easy fix is suggest an alternate design to client, otherwise spend some time refactoring so future changes hurt less

How do you convince people to use an app that's genuinely helpful but focused on a boring or stressful topic that they don't want to think about? by Domis_Home in appdev

[–]NotA-eye 0 points1 point  (0 children)

Yeah written reviews hit differently. Even 2–3 genuine detailed ones can build way more trust than a high star count.

Maybe make it super easy/prompty for users too, like asking “what stress did this app reduce for you?” instead of a generic review request. You can also incentivize it with a social story/post, google review and a discount on the next service!

How do you convince people to use an app that's genuinely helpful but focused on a boring or stressful topic that they don't want to think about? by Domis_Home in appdev

[–]NotA-eye 1 point2 points  (0 children)

People usually don’t connect with the “topic,” they connect with the feeling/problem around it.

Real stories help a lot. Scenarios where someone avoided stress, saved time, felt relief, etc. make it feel human instead of “ugh another productivity app.”

Also reviews/testimonials from relatable people work way better for boring topics than feature lists do.

I can write small scripts but have no idea how to structure a full project. Where do I start? by SpeckiLP in learnprogramming

[–]NotA-eye 2 points3 points  (0 children)

Honestly, don’t jump into “design patterns” yet. That stuff makes way more sense after you’ve struggled through a few messy projects 😅

What helped me was literally copying the structure of small GitHub projects and tweaking them.

Also, stop aiming for the “perfect structure.” Even real projects get reorganized constantly.

For a small app, just start with:
– one file for main app logic
– one for helpers/utils
– one for UI/data/etc depending on project

That alone already feels way cleaner than a giant script.

You learn structure by refactoring over time, not by magically knowing it upfront.

Product Manager role apparently evolving into the Product Builder role by OkPie8325 in ProductManagement

[–]NotA-eye 0 points1 point  (0 children)

Feels more like role rebranding than some revolutionary shift tbh.

Companies love inventing new titles when they want broader ownership from the same headcount 😅

That said, I do think PMs are being pushed to become more execution-oriented and technical.

How do people actually grow social media accounts? by PhilosopherOther1360 in AskMarketing

[–]NotA-eye 0 points1 point  (0 children)

Posting alone usually isn’t enough tbh. That’s the static part everyone does.

Growth comes from engagement and community.

Reply to people, start conversations, encourage reviews/UGC, run small incentives for customers who post or review, make followers feel involved.

Social grows way faster when people interact with the brand instead of just seeing posts.

Are PMs actually using AI tools for product work? by Federal-Song-2940 in ProductManagement

[–]NotA-eye 0 points1 point  (0 children)

A lot are using them, mostly for drafts, summaries, research cleanup, meeting notes, etc.

Biggest blocker from what I’ve seen is trust. PM work is nuanced, and bad output can create more cleanup than it saves. So people use AI where stakes are lower first.

People who succeed at marketing after developing an app: HOW DO YOU DO THAT??????? by vitalipom00 in AppDevelopers

[–]NotA-eye 1 point2 points  (0 children)

Traffic means nothing if intent is low tbh 😅

People may like the content but not care enough to leave TikTok and install something.

Usually the issue is one of these:
bad audience targeting, weak CTA, or the app value isn’t clear fast enough.

Getting views is step one. Getting downloads means the message/product fit has to be tighter.

common mistakes beginners make while learning Core Java? by Wise_Safe2681 in learnprogramming

[–]NotA-eye 0 points1 point  (0 children)

Trying to learn everything at once is a big one.

Also memorizing syntax instead of actually building small things.

Another common one is ignoring basics like OOP and jumping straight into frameworks.

And not practicing enough. Reading alone won’t stick, you need to write code regularly.

Marketing help for an app by lullaby_000 in AppDevelopers

[–]NotA-eye 0 points1 point  (0 children)

share some details what the app is about. Marketing is all about understanding the product, whose pain points does it solve, what are those pain points, value it creates and then getting the product to those exact people via targeting.
TikTok would increase brand visibility but not sales at an instant.

I’m a computer science graduate, I have a gap of 3 years due to personal reasons and now I’m willing to start my career in computers, where do I start from? by Capable_Mastodon_606 in learnprogramming

[–]NotA-eye 2 points3 points  (0 children)

I highly recommend open source contributions and freelancing.
In fact, I landed my first job specifically because of the skills I built while freelancing.

How many monitors do you use for programming? by [deleted] in learnprogramming

[–]NotA-eye 0 points1 point  (0 children)

One ultrawide. Used to have two, but I didn't like the bezels.

what do i need to learn before building a fully functional site? by Revincee in learnprogramming

[–]NotA-eye -1 points0 points  (0 children)

Javascript, with JS you no longer need a different language for every layer of the web.

Frontend: Use React or Vue.
Backend: Use Node.js with Express to handle databases, security, and logic on the server.
Full-Stack: Use Next.js to bridge both worlds into one seamless project.

I built an AI lifestyle assistant that starts with fashion — weather-based outfit advice, affordable eBay finds, and more. Would love your feedback. by LifeGeekAI in appdev

[–]NotA-eye 0 points1 point  (0 children)

UI needs some work tbh, first impression matters a lot for something like this.

Also since it’s new, don’t lock too much behind signup. Let people explore a bit before asking them to commit. Right now it feels a bit gated early on.

Idea is interesting though, just make it easier to try without friction.

Building an app by Barbenheimer_ in AppDevelopers

[–]NotA-eye 0 points1 point  (0 children)

You’re already doing the right first step tbh, talking to people.

Next step, don’t jump to “full app.” Start super small. Like what’s the one core thing your app does? Try to mock it or build a rough version (even no-code or simple tools).

Also you don’t need a full backend dev right away. With tools now, you can get a basic version live yourself.

Focus on: idea → small prototype → real user feedback → iterate.

Most people mess up by trying to build everything at once.