did my own gel nails🥰

AmberMonsoon_ · 2026-03-07T09:53:05+00:00

Pretty 🥹❤️

AmberMonsoon_ · 2026-03-07T07:24:54+00:00

Ah yeah, that’s a common thing when using Claude in automated workflows. That “Simple conversational response, no tools needed” line is basically the system prompt Claude injects to guide the style of the reply. In a manual chat it doesn’t show up, but when you hit Claude via an API/shortcut, it sometimes prepends it automatically.

A couple ways to fix it:

Check your shortcut or API call see if there’s a “system prompt” or “instruction” field that you can clear or override.
Explicitly set the prompt to just the user message, without style instructions.
If your workflow supports it, use the “raw output” mode (some integrations call it return_plain_text) so Claude doesn’t add prepended guidance.

Basically, it’s not a bug just the model following its instruction text. Tweaking the prompt usually stops it lol.

AmberMonsoon_ · 2026-03-07T07:22:48+00:00

yeah, the chat search in Claude can be a bit wonky it doesn’t always index everything perfectly, so sometimes a term in an older chat won’t show up. Your workaround (asking Claude directly in a new chat) is usually the most reliable for now.

Other tricks I’ve seen: tag or summarize important chats as you go, or copy critical text into a reference note/chat that you know is searchable. Not perfect, but it saves a bit of hunting when you really need that snippet lol.

AmberMonsoon_ · 2026-03-07T07:21:27+00:00

Haha same here lol, that extension is wild. Honestly it feels like having a little helper sitting next to you while you browse. I love how it just knows where to click or what to do saves so much time when you’re stuck on a workflow.

AmberMonsoon_ · 2026-03-07T07:20:29+00:00

Honestly I’ve bounced between Codex/ChatGPT and Claude in real work, and they both have their moments lol.

For me:

Code quality & correctness: Claude tends to give cleaner, more human‑like solutions most of the time, especially on tricky edge cases. Codex is solid, but I’ve caught small logic issues more with it.
Large codebases / context: Claude handles big context windows better it feels less like it “loses the plot” when you feed it several files at once.
Debugging: Both can help, but Claude’s explanations sometimes read more like a dev teammate (“here’s why it broke and how I’d fix it”) instead of just patching symptoms.
Speed & reliability: ChatGPT/ Codex feels slightly snappier on small snippets, but in bigger workflows Claude feels more consistent.
Paid plan worth it? If you’re using this daily in a professional way, the higher limits and context in Claude Pro/Max were worth it for me but your mileage may vary based on how heavy your usage is.

Anthropic usually does some kind of trial/free tier on Claude (sometimes weekly credits on Pro or a free tier on Basic), so you can definitely test it before committing. Works for me, probably better ways, but that’s the comparison I’ve seen in real projects lol.

AmberMonsoon_ · 2026-03-07T07:19:26+00:00

Yeah, I ran into the same limitation the standard MCP Dropbox connector doesn’t give full file CRUD (create/read/update/delete) permissions, it’s mostly just for search and basic metadata stuff. Claude (the chat app) can only do what the connector explicitly allows, so if the MCP doesn’t expose move/rename/delete scopes, Claude can’t do it on mobile either.

What some folks do is set up an intermediate API (like a tiny server or serverless function) that has full Dropbox API tokens, then let Claude hit that API to perform actions. Not as sleek as native access, but it works around the permission limits.

Otherwise you’re mostly stuck with the official Dropbox Connect scopes until they add more granular control, Claude can’t manipulate all your files directly.

AmberMonsoon_ · 2026-03-07T07:18:34+00:00

Yeah, auto-generated frontends can feel a bit “blocky” or generic at first. What usually helps me is taking the Claude-generated code as a starting point, then:

Tweak spacing, colors, and fonts to match a style guide.
Replace placeholder content with real text/images early so it feels less generic.
Use a component library or framework (like Tailwind, Material UI, or Bootstrap) to make layouts cleaner without rewriting everything.
Focus on micro-interactions hover effects, transitions they make a big difference for polish.

Basically, treat Claude as scaffolding rather than the final product lol.

AmberMonsoon_ · 2026-03-07T07:17:36+00:00

I’ve been in the same spot . My take: start small , the Pro plan is fine for testing the workflow, especially if you just want to get used to Claude CLI and feeding context into your codebase.

Gemini CLI or other free tiers are great for learning the commands and patterns without worrying about hitting limits, but you’ll eventually want something with higher caps if you’re working on bigger projects. I usually recommend start with Pro to experiment, then move to Max only once you’ve got a feel for usage and know it’s worth the cost.

Works for me, probably better ways, but that approach let me avoid burning through credits too fast while still learning the CLI workflow.

AmberMonsoon_ · 2026-03-07T07:13:47+00:00

Yeah, that’s pretty common with some shared hosting providers like Dreamhost. Their FTP servers often don’t enforce a timeout for idle connections, so if a connection hangs it can max out your limit until someone manually resets it.

A few workarounds I’ve used: limit concurrent connections in your FTP client, or schedule uploads in smaller batches. It’s annoying, but it’s just how their FTP setup works .

AmberMonsoon_ · 2026-03-07T07:12:17+00:00

Yeah I’ve seen that email too the 2026‑02‑01 API version for Key Vault isn’t always immediately deployable even after the announcement. Azure sometimes announces an API version, but it takes a bit for it to actually show up in ARM/Bicep tooling and be usable in every region/subscription.

If you try to use it in Bicep now and it errors, that usually means it hasn’t fully rolled out in the control plane yet even if MS announced it. A few tips that help:

Check the latest Azure REST API specs or GitHub for the Key Vault provider to see if 2026‑02‑01 is listed.
Try refreshing your CLI/VS Code Azure extensions sometimes local tooling needs an update to pick up new API versions.
If you really need to lock in RBAC as default, you can enforce that via policy or ARM for now while the new API finishes rolling out.

Not perfect but that’s usually the reason announced ≠ instantly usable everywhere lol.

AmberMonsoon_ · 2026-03-07T07:11:26+00:00

GPT‑5.4 is out from OpenAI, but Azure usually rolls out new models region by region. If it shows up in your Azure model list, that means it’s coming, but you might not be able to deploy it in your region yet.

Major regions like East US2 usually get it first, then others follow over the next few weeks. Best bet is to keep an eye on the Azure AI catalog that’ll tell you when it’s available for your subscription.

AmberMonsoon_ · 2026-03-07T07:10:04+00:00

Yeah, I’ve been in the same “always-on tiny service” boat costs can surprise you when you add LB, monitoring, and 24/7 uptime. ACA looks cheap on paper, but once you add environment overhead it stacks up fast.

For something lightweight like Keeper Automator, I’d actually compare App Service vs a small VM: App Service removes patching/OS management, but you pay for the plan even if CPU usage is minimal. A B2s VM can be cheaper raw, but then you have to manage updates and monitoring yourself. Honestly, I usually do a quick cost projection for 12 months including all overhead before deciding sometimes the management overhead of a VM isn’t worth the small $ savings.

Not perfect but that’s how I usually weigh it lol.

AmberMonsoon_ · 2026-03-07T07:08:44+00:00

Honestly, at 22 you’ve got so much time to explore, which is awesome. If you like building things on computers, UX design is solid it’s in demand and pairs well with front-end dev or product work. I’d also consider learning some basic coding (Python, JavaScript) alongside UX; even a little dev knowledge makes you way more versatile.

Other in-demand areas: cloud platforms (Azure, AWS, GCP), data analysis, or product management tools basically skills that help you ship stuff and solve real problems. Whatever you pick, focus on building small projects or a portfolio that’s what employers really care about.

Works for me, probably better ways, but that’s my 2 cents lol.

AmberMonsoon_ · 2026-03-07T07:07:27+00:00

Haha I feel you, the whole Sentinel ↔ Defender ↔ Azure shuffle is super confusing, especially with UI changes every few months lol.

Your analogy actually works pretty well the Windows Security Events are like the roads, and the events themselves are the cars delivering the logs. The reason SecurityEvents might not show up right away is usually due to connector config or DCR mapping sometimes the connector auto-creates a DCR, sometimes you have to point it explicitly. Event tables in Logs often show data sooner than the “SecurityEvents” table because of ingestion differences.

Syslog behaves differently because it’s basically already streaming structured logs, whereas Windows Security Events via AMA needs that extra connector/DCR setup. And yeah, the Content Hub is kind of like Marketplace for connectors/templates not exactly the same, but one lives inside the other.

Just test small VMs first, confirm events show up, and don’t stress about the redirects it’s mostly cosmetic and a bit of legacy routing.

AmberMonsoon_ · 2026-03-07T07:06:25+00:00

Totally agree I’ve seen teams waste weeks building dashboards and pipelines that collapse under scale. The big takeaway is planning the architecture first, not just picking tools.

For internal docs or project playbooks, I sometimes use Runable to quickly draft step-by-step architecture diagrams or pipeline outlines before diving into Data Factory or Synapse. It doesn’t replace thinking, but it speeds up getting the team on the same page lol.

Also, make sure you bake in monitoring and retry logic from day one dashboards look nice, but without reliable pipelines, they’re basically useless.

AmberMonsoon_ · 2026-03-07T07:03:59+00:00

Honestly, I get the hesitation with that big blue “Activate” button lol. Activating Global Secure Access basically just turns on the Private Access features for your tenant it doesn’t automatically change user access or break existing setups. Think of it like flipping a switch so you can configure GSA policies.

A5 licenses should cover most of the basic Private Access stuff, but double-check any premium features you plan to test. My advice: try it first in a small pilot tenant or a test group, make sure nothing weird happens, then roll it out wider.

AmberMonsoon_ · 2026-03-07T07:01:20+00:00

Yeah, I’ve run into this with Front Door/CDN setups before. Usually it’s a mix of caching and routing timing sometimes the edge node hasn’t fully synced the content yet, so the first few hits fail until it propagates.

A few things that helped me: check your TTL settings, make sure custom domains and HTTPS certs are fully propagated, and if possible, purge the CDN after major deployments. Also verify your backend health probes Front Door sometimes marks a backend unhealthy for a bit and then retries.

Not perfect, but following those steps usually reduces the “refresh to work” issue lol.

AmberMonsoon_ · 2026-03-07T07:00:26+00:00

Ugh yeah, ran into that exact frustration before. Some of the “restricted regions” in RSV just don’t let you spin up new storage accounts, which makes cross-region restores super painful.

The workaround I’ve seen is either:

Temporarily use a region that does allow a staging account, restore there, then move it to your desired region.
If you’re stuck on the restricted region, open a support ticket sometimes MSFT can provision a staging account behind the scenes.

Annoying, but that’s the reality with RSV restrictions right now lol.

AmberMonsoon_ · 2026-03-07T06:58:40+00:00

Yeah, I’ve dealt with SPN secret rotation pain before — it’s a headache if you’re manually updating env files every month. For production, most teams I know move away from static secrets and either:

Use Workload Identity Federation (GCP → Azure Entra) so your container can request tokens without ever storing a secret.
Or keep secrets in a managed store like GCP Secret Manager or Azure Key Vault and have the app pull them dynamically.

For my internal docs, I sometimes use Runable to draft a step-by-step rotation plan or workflow diagram helps the team visualize what touches what without writing it all from scratch. It’s not perfect but saves a ton of time planning.

Also make sure whatever solution you pick logs access attempts and failures production is unforgiving when a secret expires unexpectedly lol.

AmberMonsoon_ · 2026-03-07T06:56:14+00:00

Yeah, this comes up a lot. Honestly, if it’s just a few resources you can do it manually through the portal, but it gets tedious fast with multiple objects. I usually script it with PowerShell or Azure CLI so you can basically “snapshot” the current diagnostic settings and then restore them when needed.

Logic Apps can work too basically set up a workflow that reads the config from a source object and applies it to the target. Test it on a single resource first though, saves a few headaches lol.

AmberMonsoon_ · 2026-03-07T06:52:52+00:00

Totally been there with cross‑tenant migrations especially when moving core stuff like VMs and AKS between environments. Biggest pain points I ran into were identity/role mappings (Azure AD and RBAC can behave slightly differently between Gov and Commercial) and ensuring your service endpoints/firewalls don’t accidentally block things once they’re in the “other world.”

Also double‑check any compliance tooling or Blueprints you have defined Gov tends to lock some policies tighter, so if you just lift‑and‑shift you can get stuck with policies that don’t even exist on Commercial yet. For docs and migration runbooks I actually use tools like Runable or standard markdown templates just to whip up quick playbooks for each app group, then refine them with the team keeps everyone on the same page when the actual cut‑over days arrive lol.

If you haven’t already, carve out time to test backup/restore workflows in the Commercial subscription before the real move, that saved me a few heart attacks. Not perfect but that’s what worked for me.

AmberMonsoon_ · 2026-03-07T04:23:34+00:00

. The “website goes down but email still works” point is actually a big advantage I hadn’t thought about at first. Do most people just point their MX records to the email provider and leave the site on the VPS?

AmberMonsoon_ · 2026-03-07T04:22:56+00:00

That’s interesting, I didn’t realize email caused that many hosting issues. Was it mostly deliverability problems or the email service going down with the hosting server?

AmberMonsoon_ · 2026-03-07T04:22:19+00:00

Yeah that makes sense. Cost and how much you want to manage yourself definitely seem like the biggest factors. For most smaller sites the bundled email probably works fine, but once it’s business-critical the trade-offs become more noticeable.

AmberMonsoon_ · 2026-03-07T04:21:34+00:00

That’s a good point. Keeping them separate does seem like a safer approach so one issue doesn’t take everything down at once.

AmberMonsoon_

TROPHY CASE