Pages

Wednesday, July 9, 2025

Operation Night Sting

After spending Independence Day weekend with the in-laws, my family and I returned home, ready to settle back into our routine. I’ve been sticking to a ketogenic diet lately, so like usual, I fired up the grill in the backyard to cook some patties.

That’s when I noticed a bee hovering a bit too close for comfort. Normally, these things follow me for a few steps and then lose interest. Not this one. It tailed me all the way into the house. When I went back outside to flip the burgers, there it was again. Same thing happened later when I stepped out to do some light yard work during my lunch hour.

My wife came home after picking up the kids and sure enough, she was harassed too. We assumed it might’ve been a deer fly, since we’ve had a deer hanging around the property lately. But after dinner, during our usual evening walk, a few of them came at me again, bouncing off the back of my head. I bailed and headed inside. My wife kept walking, but not for long and she got stung on the nose. She came back in with a few of the pests still on her shirt and confirmed: honey bees.

The nearest neighbor is between a quarter and half a mile away and they keep bees. We’ve dealt with them before. They usually give us a heads-up when they’re treating the hives for mites because the bees get agitated. So we gave them a call.

Turns out, the neighbor’s son—the beekeeper—had recently transported the queen to another location across the state and accidentally dropped a bunch of bees in the process. Without their queen, the remaining bees were angry, disoriented, and had started harassing us every time we stepped outside. From what we researched, this kind of behavior could continue for up to two weeks until they died off. Problem is, we had things to do and we couldn’t spend two weeks under siege.

With permission from both the neighbor and her son, I was cleared to exterminate the bees. The plan was to do it around 9:10 p.m., once they’d returned to wherever they were nesting for the night. These bees were already doomed without their queen - I was just speeding up the process.

But first, I needed to find the hive.

I charged up the drone and flew it over the suspected area. The drone got swarmed, but I got it back safely and managed to spot part of a box where bees were gathering. I drove over to confirm, and the car was attacked too, but I had a fix on their location.


At 9:10 sharp, I suited up: overalls, sweatshirt, long gloves, and a headlamp. I grabbed my poison of choice: a mix I always keep on hand: water, surfactant, and Demand CS, a long-acting insecticide. It doesn’t kill on contact but works over the next few minutes or hours and stays effective for up to 30 days. It saved me from an elm seed bug invasion a month ago.

I crossed a low spot in the fence and crept into the tall grass, accidentally spooking a baby deer in the process. Found another low gap in the next fence and made my way to the box near a Russian Olive tree. No activity. Still, I sprayed the tree and the box thoroughly and flipped part of it over. Nothing. Sprayed again for good measure.


On my way back, I spotted a fence post absolutely swarming with honey bees. Jackpot! I sprayed it hard. As I turned to take some photos, they got loud, real loud. I sprayed again and got the hell out of there. One even followed me for a bit on my retreat.


The next day? Quiet. No bees. No one in my family has been bothered since.


Thursday, May 29, 2025

The Battle of Saigon [Not Ho Chi Minh]

I've got a stream running through my front yard that seems to be fed by an underground aquifer. I don’t know for sure if someone accidentally hit it trying to dig a well years ago, but it’s only about 12 feet from my well house, so it wouldn’t surprise me.

This stream has basically turned into a little problem, and now it’s being overrun by Russian Olive trees. If you’ve never dealt with them, they suck—literally. They’ve got nasty thorns, and if you cut them down, they come back like Wolverine. I’ve also got a few good trees near the stream that are losing out because these Russian Olives hog all the water and sunlight.

The stream used to feed a small pond, but now the pond’s not getting enough water. I’ve had to supplement it from a secondary source, which is not ideal.

Clearing this mess sounds simple—just cut the trees back—but it’s kind of a dangerous job. I need to remove the Russian Olives and any other junk trees growing around the stream, right down to the ground, so the stream can flow properly and the good trees have a chance. The problem is, if I slack off for even a year, it’s game over. They’ll grow right back and undo all my progress.

There are ways to slow them down—like hitting the fresh stumps with glyphosate—but I don’t really want to mess with chemicals near a water source, especially since I’m hoping to fish that pond one day.

I’ve got a big dumpster, but only about half of it is free because my family fills the rest with household trash. That’s not going to cut it for all the brush. I’ll need to burn a lot of this stuff, but my window for doing that is limited each year. So I’m also going to have to load up my truck bed and make regular dump runs. Most dumps now require a tarp or some kind of cover over your load, so I’ll have to deal with that too.

This is my front-yard battle of Saigon.



Wednesday, October 30, 2024

Quantum Disbelief

A couple of years back, I hopped on board with a tech firm I'll call IntellectY (not the real name, of course). They welcomed me with a bunch of swag and a ton of accolades, claiming I’d be tackling a national crisis. The pay was good.


The onboarding process went smoothly. I was assigned a colleague and a project manager, and I only had to attend one meeting per week. The company organized a weekly two-hour session where everyone would share updates on their projects, which felt odd to me as most of them would boast about what their product or feature could do for the future. I prefer focusing on the tasks I've completed rather than discussing their potential impact, as I'm more of a straightforward, action-oriented person. Over time, these meetings became bothersome, and I realized that some felt similarly.


The first red flag I noticed was the CEO's murky legal past. One of his cases even made it into a college law textbook, highlighting how he and his wife lived beyond their means, writing off lavish expenses, dinners, and trips.


My first ethical challenge at IntellectY arose when we began marketing our product as "quantum" technology designed to alleviate port congestion. In reality, genuine quantum technology should utilize quantum computers for faster problem-solving, but we were essentially bluffing. Our API did have the capability to connect to DWAVE, a company known for its quantum annealer, but we had disabled that feature long ago. When it was active, DWAVE's system would time out 90% of the time, and the remaining 10% of the results were useless compared to our original engineer's messy yet effective classical code. DWAVE itself has a questionable legal history, sometimes accused of making dubious claims about their technology.


One day, a former colleague alerted me that our client might be trying to reverse engineer our solution, specifically the truck appointment system and container stacking logic. The logs indicated that this was probably accurate, as our test lane API was being accessed frequently from a location in India, where their database engineer was based. This engineer, known for creating their problematic unnormalized system, had a reputation for being particularly challenging to collaborate with, especially when problems occurred. In the end, the claim that they reverse-engineered our solution did not stand up during mediation.


On a separate occasion, our database encountered a problem while I was preoccupied with other tasks. A data scientist, who preferred not to be referred to as an engineer, was working with machine learning on the database and inadvertently created an uncontrolled table. This resulted in excessive SQL Server charges for the client due to the unchecked expansion of the table. Consequently, the client received a hefty bill. It was quite embarrassing for me because we billed the client $6,000, an amount that could have easily been reduced by half.


In the spring, the client notified us that they no longer needed our services, and our company took legal action. My project manager was dismissed for falsifying his progress, and another colleague was also terminated. The situation grew increasingly tense.
Following these events, I was reassigned to a Python project focused on AI for document-based user interactions. However, as a .NET (C#) Engineer specializing in SQL Server, I have no interest in Python development.


Our Python/React app enabled users to chat with their documents but always depended on third-party LLMs. One day, the owner started claiming we were offering a RAG or even our own LLM, leading the industry. He tended to exaggerate. I can't count how many client meetings I attended where I saw disbelief.


I was once instructed to spend more than a month developing an integration with a major storage web app, only to later discover it was for Azure Gov, which we couldn't access. If we had known this sooner, it would have saved us a significant amount of effort.


I anticipated a conflict with the lead Python developer, a young man with different ideas and an overcritical attitude. Refusing to work with such personalities, I stepped back and let him handle the pressure. Surprisingly, this led to his resignation, and I ended up taking over his role, which I didn't enjoy. I became proficient in Docker, React, and Python, despite my lack of interest. Ironically, we became friends later on (shared misery?).


The company struggled, losing contracts and facing financial difficulties. On the departing developer's last day, the owner promised to hire five more developers, likely because the developer aspired to lead a team and it was a ploy to show him we were growing. However, no new hires were made, and the financial situation worsened. The young developer advised me to heed the Chief Science Officer's sarcastic comments during morning meetings, as they often contained truth.
I closely listened to the CSO's remarks, which were revealing. He claimed the company could last two years financially, but I suspected only one year was the real truth. He joked about the owner's ventures leading to financial ruin, which proved true for him, as he drained his 401k on speculative projects and trendy buzzwords.


The organization appeared to generate revenue through two main avenues: patent litigation and government grants. While the income from patent litigation was relatively small, the government grants were moderately profitable. The company would employ trendy terms such as neural-network, quantum, natural language, unstructured data, and deep learning to market fake products. This strategy often secured them a Government Proof of Concept Contract, potentially worth hundreds of thousands of dollars. Eventually, the government would catch on, typically within 3-6 months, and terminate the contract—though the company would still receive payment. Despite this, the company was never blacklisted, allowing them to repeatedly exploit the same grift against the Government. The organization would later employ a third grift to try to gain money from "quantum" investors.


I admired the CSO and see him as a victim in this situation. He was kind to me and managed my workload until he couldn't protect us anymore. As an early investor, he put a lot into the company, using his 401k and savings. I feel bad even mentioning this.


One day, I was asked to help the owner's partner company with database work, but I refused as I wasn't employed by them, deeming it unethical. Despite working weekends and implementing a large language model for a client, the company's financial issues continued. The owner's suggestion to "open source" the entire company was absurd and shattered my remaining faith.


They illegally withheld three paychecks, later reimbursing only two, and never matched 401k contributions. I thought about quitting earlier due to constant priority changes and overwhelming workloads. They misled clients with non-existent products, and I had to handle the aftermath. After learning about financial issues, I resigned. 

The company was creating another bogus product, filled with trendy buzzwords like neural networks. It was no better than a basic Windows Desktop search. They aimed to pitch it to government agencies and quantum investors, though it likely wouldn't function well and would be easily outdone by other offerings.

In my exit interview, I refused any offers to stay.
I chose to leave on "friendly" terms, sending a gift to a developer and a goodies basket to the CSO, who was also misled. I'm still friends with everyone except the owner and will miss many, including the data scientist who is now facing tough times.


The company’s mediation with a former client failed. They had relied on a settlement, but it backfired when a contract clause was not honored. The company now only exists in name only. Anyone working there is entirely doing it for free (by the time anyone reads this).


A few days after I resigned, another colleague did the same. I might take the CSO out for lunch soon. I feel terrible for him—his retirement and dreams are shattered.

Monday, July 15, 2024

Hair Loss (6 Months)

6 months on oral minoxidil 2.5mg, once a day. 

This is after a buzz cut. Wife was impressed with the results. I think the 9 month or 12 month results will ultimately be the decider of whether I should continue.

I slowed down the red light therapy and topical rosemary applications as I've been busy, but I will try to reincorporate.





Monday, January 15, 2024

Hair Loss (BEFORE)

Picture of crown (buzz cut)
 I've noticed my hair thinning, and while it used to bother me more, I've reached an age where I'm not as anxious about it. Around 85% of men will lose a significant amount of hair by age fifty.  If this had happened in my twenties, I'd be in full panic mode. In my early thirties, I managed to slow down hair loss with topical minoxidil, despite experiencing some side effects. However, it's no longer effective.

Starting January 12th, I've adopted a new routine, and I'll share my progress in three and six months:

1) Switching to oral minoxidil, as it's said to absorb better and has shown regrowth results (prescription required). Whereas topical minoxidil seems to only be effective at slowing down hair loss.

2) Using topical rosemary oil mixed with coconut oil, proven as effective as minoxidil in one study.

Picture of Crown (No Haircut)

3) Micro-needling every two or three days.

4) Red light therapy every other day (though my device isn't top-notch yet).

5) Applying Jamaican castor oil every three days.

6) Using caffeinated shampoo every three days.

7) Taking a daily saw palmetto pill (DHT blocker).


I've tried various other remedies like biotin shampoo, different DHT blockers, and natural shampoos with no success. This new approach might either work or not, but I'm determined to find out.

Note: Both pictures were taken one day apart. The top left photo is with a buzz cut and the bottom right photo is without a haircut. These are my starting photos.