Books used to be my primary way of learning. Wasn't much out there online teaching you how so it was a lot of trial and error. But now-a-days, I find it helpful to tell AI "hey, I'm new to this. Explain things to me line by line. No bullet points." and it always explained things really well for the new stuff I hadn't run across before.

getDay() returns a number, not a string. If you want a string, you'll need to convert that number to a string using a list index. But then you can remove all of the switch and do: const days = ["weekend", "Monday", "Tuesday", "Wednesday", "Thursday", "Friday", "weekend"]; let date = new Date(); let result = "Welcome to "; if ((date == 0 ) || (date == 6)) { result = result + "the "; } result = result + days[date.getDay()] + "."; console.log(result);

I can't share my project .... yet. It's owned by me but not ready to be talked about yet. But, I'm learning about building NextJS apps that are very modular and how this reduces CSS and coding repetition. Also learning about user workflow and how not to scare a customer off. For example, I noticed that I was repeating a lot of CSS for each button ... I didn't have many buttons (yet) but it was becoming a pain separating them. So, we built a generic button with base CSS values and animation and then just fed it the link, colors and text to display. I wiped out 4 files of CSS all at once. 😁

@Zohra Hashmi Vibe coding is a way of building software by describing what you want in plain language and letting an AI generate the code for you. 🌱 What “vibe coding” actually means Vibe coding is a style of programming where you tell an AI what you want, and the AI writes the code. Instead of typing out every line yourself, you guide the AI through prompts like: - “Build me a login page with email + password.” - “Fix this error.” - “Add a dark mode toggle.” The AI generates the code, you test it, and then you refine it by giving more instructions. This conversational loop is the core of vibe coding. 💡 Why people call it “vibes” Karpathy described it as “forgetting the code even exists” — meaning you focus on the idea and let the AI handle the implementation. It’s not about being sloppy; it’s about shifting your role from coder to director. 🚀 What vibe coding is good for Great for: - beginners who want to build things without deep syntax knowledge - rapid prototyping - “weekend projects” - experimenting with ideas quickly Less great for: - production systems that require strict security - long‑term maintainability - situations where you must fully understand every line of code Critics warn that relying too heavily on AI‑generated code can introduce bugs or security issues if you don’t review it. Vibe coding is like telling an AI what you want your app to do, and it writes the code for you. You guide it with prompts, test what it gives you, and refine it. It’s great for beginners because you don’t need to know every programming detail — you just describe your intent.

@Rob Vanarsdall I wouldn't say I have years in development. I've done little things here and there over the years, but my primary job was/is a chemist/lab support in a pharma plant. Sure, I've written a whole Excel program but outside of many small LIMS programs, I've not done a lot. It's only recently that I've gotten really into programming because our site is shutting down and I'm changing careers. But I've learned a lot from books and sites over the years - some now outdated but a lot is new. I have a good memory for things - not so much the 100% details but very good where to find the information. And I'm not afraid to ask. I don't care if people think I'm dumb for asking .... doesn't bother me .... I'd rather ask and get it right the first or second time. As for now, I'm learning new things every day. A week or two ago I learned how to get Clerk running. Got my own Prisma and DB built. And just yesterday about NextJS CSS modules and why I don't need them right now. Learning is where you find it in your journey. One needs to be open and willing to explore a little. Sometimes it's 5 minutes .. sometimes a few days to learn and understand something enough to actually use it well. As for being lazy .... well, not much time for that. But, a good anime fills the time nicely when I'm taking a break.

There is both good and disaster with single sign on. We use SSO at work all of the time. But, at work, we are behind firewalls (several in fact), some servers and systems are only local with no internet access and others are global systems. But, like I said, all are behind overly secure firewalls because they are pharma and just can't have a breach. But these personal SSOs .... well, therein lies a huge issue which I think your image points out. If you use SSO for 2 or more things, once your compromised, the attacker has access to everything. Your world could turn into a nightmare in less than 5 minutes. But sure, some are turning to 2 factor authentication now ... but, that only really works if it stores your IP address and doesn't recognize the device you're on (which I'm not sure all do). But, if it's got your IP address, does that make it worse?

@Rob Vanarsdall Yeah. Personally, I detest 2 factor. I'm not the kind of person who has my phone on me 24/7 so having to go get it to log in is really, really annoying. Sure, I like that you won't be able to change some of my personal information without confirming who I am ... but why do I need that in order to log in? Every. Bloody. Time. Maybe what is needed instead is to teach people about cyber security along with programming. Learning to secure your database. How to check up on security risk. .... and maybe fund some of these open-source projects so people will actually patch up the holes.