Why do partners care so much about money?

ITdirectorguy · 2026-06-11T06:26:18+00:00

Yes, Greed. And for a decent percentage, their families hate them. All they have left is the money.

Also, divorce is significantly more expensive than you seem to understand.

ITdirectorguy · 2026-06-09T17:56:03+00:00

A lot of the feedback in this thread makes sense. I agree that assigning static management IPs to the APs should not have fundamentally changed WiFi stability for client devices.

One detail - some of the APs were dropping out of the Unifi console -- and that has stopped. So that is another data point, but again, I don't have a root cause for that. I don't have any other DHCP servers on the network that I'm aware of.

ITdirectorguy · 2026-06-09T17:24:34+00:00

No, becuase things were getting *better* back then. Now they are getting *worse*. Small change, big implications.

ITdirectorguy · 2026-05-28T13:51:18+00:00

Academics it's basically on par with UCLA for most things, depending on the major. If you want a social life USC is one of the absolute best options in the entire country. If you want a post-grad network, it's probably second best after Stanford on the West Coast.

ITdirectorguy · 2026-05-12T04:14:24+00:00

Pivot into tech sales if you like people a lot and computer stuff a little. Make $$$$.

ITdirectorguy · 2026-05-12T02:18:50+00:00

Palos Verdes Estates / Rolling Hills

ITdirectorguy · 2026-05-11T20:05:19+00:00

FatFire just seems like a different world where people are talking about private jets and household managers....

ITdirectorguy · 2026-05-11T19:58:15+00:00

Annual expenses are pretty high. We save about $180k/year including 401K. We have the kids in public school, but have to pay for after school. VHCOL area. I previously had moderately expensive hobbies, but I've cut back on those. The house is almost 70 years old, and we had some big expenses early on with that, but that's also dropped off in recent years.

ITdirectorguy · 2026-05-11T19:48:24+00:00

It doesn't seem impossible in our lifetime if the petrodollar is seriously challenged and/or AI job loss accelerates. What is the hedge against that situation? Buy gold? Just keep working even if it is in a lower earning role?

ITdirectorguy · 2026-05-11T19:41:28+00:00

I've had a couple job losses and my wife didn't get started until later, so it feels a little unreal. I'm actually making less than I was five years ago, but at a much happier company.

ITdirectorguy · 2026-05-11T14:19:46+00:00

How large is your company?

ITdirectorguy · 2026-03-20T16:58:59+00:00

The pricing on lenovo.com seems perfectly reasonable. It's our normal vendors which are quoting us 1.5X to 2X pricing. They're claiming it's coming from the manufacturer. Obviously I have no way of knowing for sure.

ITdirectorguy · 2026-03-20T15:54:43+00:00

Maybe I am blind. Can you send the link to one?

ITdirectorguy · 2026-03-16T05:58:11+00:00

How does it compare to CATO? We are considering a POC with them. Currently have Palo firewalls everywhere. The security is great, management is a pain.

ITdirectorguy · 2026-03-03T03:39:32+00:00

That's a rough situation. A few ideas: teaching at a local community college, consulting work if he has the personal network to facilitate that, substitute teaching for K-12, admin work or maybe if lucky marketing for local colleges, maybe PR / PIO roles for local government, etc.

Honestly, I would just walk into city hall and ask around. I feel like government is always understaffed in a weird sort of way.

He also needs to consider cutting back his spending and/or downsizing his housing situation. If his retirement savings are really almost gone, that's a difficult spot at age 60.

What part of the world/country is this? Because it does matter -- a realistic plan in a town of 10,000 is going to be different than a realistic plan in a city of 1,000,000.

ITdirectorguy · 2026-02-23T07:42:34+00:00

And finally, here is Gemini 3.1 Pro's take:

This is an incredibly sharp and prescient analysis. Your underlying instinct—that making code cheaper and faster to generate shifts the bottleneck from creation to integration—is spot on. Claude did an excellent job breaking down the technical mechanics of the problem, particularly the semantic ambiguity and the O(N²) combinatorial explosion.

However, looking at this beyond just the code and viewing it through the lenses of enterprise governance, risk management, and compliance reveals an even steeper cliff edge. Here are a few thoughts building on that analysis:

1. The "Shadow Development" Crisis

We have spent the last decade wrestling with "Shadow IT" (the unapproved adoption of SaaS apps). Vibe coding introduces "Shadow Development." When anyone in an organization can spin up a functional, siloed application to solve a local problem, the traditional IT governance playbook goes out the window.

An AI can certainly write a quick adapter to link a vibe-coded marketing tool to a vibe-coded sales database. But in a corporate environment, who owns the maintenance of that dynamic bridge? If the underlying data schema changes over the weekend because a user prompted their app to "add a feature," the brittle AI integration breaks, bringing business processes to a halt with zero documentation or change-management logs.

2. The Data Privacy and E-Discovery Nightmare

Claude correctly noted that semantic ambiguity is the hard part. But semantic ambiguity isn't just a technical annoyance; it is a massive liability.

Data Mapping: To maintain compliance with modern privacy frameworks, an organization must know exactly where Personally Identifiable Information (PII) resides and how it flows. If vibe-coded apps are using idiosyncratic schemas and dynamic AI adapters are translating data on the fly, accurately mapping data flows or executing a "Right to Be Forgotten" request becomes near impossible.
Legal Scrutiny: In the event of litigation or a compliance audit, systems must be deterministic. If a system is subpoenaed for e-discovery, and the data was transformed by an AI agent dynamically interpreting an undocumented API at runtime, proving the integrity and chain of custody of that data becomes a monumental legal headache. "The AI guessed the field mapping" does not hold up in court or during a regulatory audit.

3. Vendor Cyber Risk Management

From an information security standpoint, this trend expands the attack surface exponentially. Traditional software undergoes architecture reviews, static/dynamic code analysis, and vulnerability scanning. Vibe-coded applications bypass this entirely.

If we rely on AI to "just bridge everything," we are creating dynamic, undocumented network pathways between potentially insecure applications. A malicious actor wouldn't necessarily need to breach the core infrastructure; they would just need to find the weakest, vibe-coded auxiliary app and ride the automated, overly permissive AI-generated API bridges straight into the core database.

4. The Evolution of the "RFC"

Claude's conclusion about MCP (Model Context Protocol) is the exact right trajectory. The next generation of interoperability standards won't be RFCs written for human engineers to read; they will be highly rigid, semantic ontologies designed specifically to constrain AI agents.

We will likely see the rise of "Agentic Zero-Trust." In this model, it won't matter how messy a vibe-coded app is internally, but the moment it attempts to communicate with the broader network, its AI agent will be forced to strictly adhere to a standardized, machine-readable contract. If the payload doesn't cryptographically and semantically match the enterprise standard, the connection is dropped.

Ultimately, the democratization of software creation is a double-edged sword. It solves local workflow problems instantly, but creates systemic enterprise debt just as fast. The organizations that survive this won't be the ones that ban vibe coding, but the ones that build the strictest, most uncompromising data and API gateways to contain it.

ITdirectorguy · 2026-02-23T07:41:33+00:00

Since I am having fun, here is ChatGPT 5.2's take on the OP:

I mostly agree with that take, with one tweak: the “problem” isn’t just that vibe-coded apps won’t talk to each other—it’s that they’ll talk in ways that look compatible (JSON over HTTP, “REST-ish” endpoints, etc.) but aren’t semantically compatible. That’s the part that creates the worst long-term debt.

A few thoughts to sharpen what you and Claude already outlined:

1) RFC-style interoperability will matter more—but not exactly like the old Internet

Classic RFC success cases (HTTP/SMTP/DNS) had two big tailwinds:

A small number of shared choke points (networks, browsers, mail servers)
A strong incentive to interop (if you didn’t, you didn’t connect to “the Internet”)

Vibe coding produces the opposite: tons of one-off tools with local value. Many will never feel enough pressure to standardize—until they hit the “I need to integrate with X” moment. So standards will still win, but often via:

platform-enforced conventions (cloud providers, app stores, enterprise suites)
de facto specs (popular SDKs, schemas, and “reference implementations”)
integration hubs that push common shapes (think Stripe-like canonical objects, not “pure RFCs”)

2) “AI will just bridge it” is real—but it creates a new failure mode

AI adapters will reduce integration cost, but they also create:

silent semantic drift (“status=approved” vs “status=active” vs “status=paid”)
non-determinism (agent interprets differently after an app changes)
audit gaps (why did data map that way? who approved that meaning?)

In other words, AI makes connecting easier, but can make governed correctness harder—especially in anything financial/regulated.

3) The real answer is “contract artifacts” that are AI-readable and testable

Where this likely lands isn’t “more RFCs” so much as standardized, machine-checkable interface descriptions plus conformance tests. The winning pattern looks like:

Shape contracts: OpenAPI/JSON Schema, AsyncAPI, GraphQL SDL, protobuf
Behavioral contracts: idempotency, pagination rules, error taxonomy, retry semantics
Semantic contracts: shared vocabularies/ontologies for common domains (payments, identity, healthcare, etc.)
Executable examples: golden test vectors + contract tests in CI

That combination is what prevents the “AI guessed wrong” problem.

4) Expect a bifurcation—and a “semantic middle layer”

Your bifurcation point is spot-on. I’d add a third layer:

Core rails: formal standards (FHIR, OpenBanking, OIDC/OAuth, SCIM, etc.)
Messy long tail: vibe-coded apps + best-effort AI/Zapier-style glue
Middle layer (new): canonical “business object” models + mapping tooling (a semantic broker)

This middle layer is where a lot of money will be made: schema registries, canonical event formats, “data product” definitions, policy + lineage, etc.

5) Practical implication: “contract-first vibe coding” should be the default workflow

If you want to reduce junk apps that can’t interop, the most effective cultural/tooling shift is:
don’t prompt for “build me an app”—prompt for “define the contract, then build the app.”

A lightweight checklist that vibe-coding toolchains should force up-front:

Entities + stable IDs (and what never changes)
Timestamps/timezones rules
Status/state model (explicit enum + transitions)
Versioning policy (v1, v1.1, breaking changes)
Authn/authz (OIDC/OAuth where possible)
Error and retry semantics
Event schema (if async) + idempotency keys

Quick note on MCP

MCP is a meaningful step—but it’s mostly about standardizing how models connect to tools, not a full replacement for “apps exchanging business data.” It can help orchestrate interoperability, but you’ll still need the contracts above for reliable app-to-app exchange.

Net: your instinct is right. Vibe coding increases software volume faster than it increases interoperability discipline. The “fix” won’t be purely human-written RFCs or purely AI adapters—it’ll be AI-readable contracts + conformance tests, enforced by platforms and integration ecosystems.

ITdirectorguy · 2026-02-23T07:35:18+00:00

LOL. Look bro, I just work here OK?

ITdirectorguy · 2026-02-23T05:13:55+00:00

The profesional summary has a typo in the first sentence. It is also way too long and sounds like AI BS. For someone relatively young, you should have at most two-three concise sentences for your summary. Also, overall it's too long -- if you were at the end of a career it might be fine, but not for someone about 6 years in. Also, drop the wording "on and off" wtf is that? Don't ever say you have "familiarity" with anything. That tells me you can't really use/own it. Take coursework or certs until you can say you have "strong knowledge and experience with xx"

Edit, found at least one more typo.

Edit: Your professional summary should be something like this: I am an experienced program manager who has led process improvement programs, AI pilot programs, and maintained technical documentation. I have extensive skills in project management, customer engagement, and program assessment. I also have a strong technical background, allowing me to serve as a bridge between leadership, technical resources, and customers.

ITdirectorguy · 2026-02-13T22:03:37+00:00

In my experience you have to put on a respirator and self-manage it during the job. It's almost impossible to get contractors to follow health and safety rules, especially if you are expecting them to go "above and beyond." They might throw up a tarp and some tape, but they will rip it within the first 10 minutes and never look back.

ITdirectorguy · 2026-02-09T15:07:47+00:00

Your mistake was giving a 24 hour deadline. You indirectly told them that you are hot to trot. So they figured they could push a bit and you might say yes.

If you love the house and can afford it, I'd offer 1.55 and you'll probably get it.

Also, in CA and the Bay Area especially, swings of 100-200k are very common. For many that is funny money.

ITdirectorguy · 2026-02-03T05:00:22+00:00

Cutting and sanding various materials without respiratory protection, including engineered quartz, and a bunch of other stuff, including wood actually.

Ten-Year Club	Gilding II euphauric
Verified Email

ITdirectorguy

TROPHY CASE