Skip to main content


Are you ready to go down the rabbit hole? To visit a surreal world, where black is white and white is carrots?

A friend, Metacognician in Shanghai, describes the situation as follows: “Life is more absurd than movies. I've gone down the rabbit hole too, when it just becomes more and more strange and you wonder how that all is supposed to make sense.” I asked him if I should just embrace it. He answered, “Why should you ... change the universe?”

It started with a psychotic named Jim Kiraly who resides, we think, at 6329 Twinberry Circle, Avila Beach, California.

Jim Kiraly is a respected citizen. A churchgoer. A Vice President of Transamerica Corporation. And a violent abuser who tried to use an emergency anti-violence measure, one intended to protect battered women, to stop his victim in a wheelchair from writing a book.

Concise enough? :)

For attorneys: Jim Kiraly filed for CLETS against his son and victim, who lived 200 miles away, did not own a car, and was in a wheelchair. His son and victim was not asked to end communications. Jim had no (zero) specific and relevant allegations that were not perjury. But he turned down repeated offers of no-contact and a signed stipulation that gave him everything but CLETS. He insisted on CLETS if his victim ever once “discussed” him with third parties.

In the end, Jim Kiraly signed an agreement far weaker than the ones he'd been offered.

A review of Court paperwork and other materials will tend to confirm that Jim and other parties, including attorneys on all sides, committed multiple felonies, crimes, and faux pas. :P

The word “abuser” is stated here publicly and without equivocation. A formal offer is hereby made to reaffirm the word in writing and under oath. Attorneys will understand the significance of the point. In short, there is little terror of a threatened defamation suit on this side. Actually, we feel that such a suit will fit nicely up Jim Kiraly's abuser ass.

Jim has one son, Ken Kiraly, who invented the Amazon Kindle and is one of the leads at Amazon's secret Lab126. Another son, Tom Kiraly is one of the leads, a Vice President-CFO type, at medical insurance firms, including one of the largest, Humana Corporation.

These people and some of the biggest names in Silicon Valley legal circles have committed or are involved in multiple crimes.

For the next decade or two, we're going to explore the crimes that these people committed, the motivations and the denial involved, the background and histories that led each person to make the choices that they did, and ways to build upon what happened and move towards positive societal goals.

There's plenty to go over. These people committed or were involved in: Spousal abuse, child abuse, DDOS (a highly prosecutable violation of CFAA), extortion, perjury, conspiracy to commit perjury (a possible felony), false police reports, conspiracy to file false police reports (a possible felony), unlawful threats, barratry, defamation, malpractice, civil harassment, criminal harassment, abuse of process, and violations of SCCBA Professional Standards.

The point was to force Jim's oldest son and victim, me, to sign a gag order. I was in a wheelchair. I'd never made a single inappropriate threat against my abuser. I wasn't even asked to not to call anybody. But Jim threatened to put me in a violence database unless I agreed never to write about him.

I won the right to write, but I lost my home of 25 years, most of my possessions, my chances for retirement, everything. Everything but a realization.

I can make a difference. I can conduct research for legitimate and reasonable purposes, document what happened, and analyze the choices of the people involved:

Maggie told me that she didn't know what she could say to me about what happened. However, we have decades to work it out. It will be productive. I'd like to direct the attention of attorneys and other parties to the:

Legitimate and Reasonable Purposes List

Questions or comments are welcome. For technical notes and disclaimers, click here.

Free Downloads

The current free ebook is located at this link:

For details about the ebook, click here.

The point? “The story is already out there, idiots. Keep it up and I'll demonstrate how something known as decentralized distribution works.”


Thursday 2012-11-15 — Flow is Not Slow

121115. Swizec is working on a book that discusses the concept of “flow” as it applies to software development. He asked for comments and I'll post some here. They're addressed to the author.

The book's home page is:

As of 121115, drafts of the book were located at:

* Perhaps the text that defines flow should be moved up to precede the Ayrton Senna anecdote.

* Holding an entire program or at least large structures in one's head: Yes. I've tried to explain to people before that this is what I do. For me the process isn't necessarily about “writing” code. It's more about moving an object that already exists piece by piece from mental space to online space.

I'm wary of mental models that come across as popular psychology. However there may be something to the notion that I need to be in the flow state, absorbed and even swept away in the current, for the process to proceed rapidly.

* I'm not sure it's correct that the developer “must feel a sense of purpose, even joy, in what they're doing” to be caught up in flow.

It's possible that what I experience is pure joy of an inarticulable sort. I perceive it as a state of being. It is what I am and what I do.

* Phenek (a pseudonym for a startuper) offers the following comments. These are his points as opposed to mine:

this flow has been discussed quite often lately relating to productivity and interruptions. many people were saying that it might take many hours to get “into the flow”.

short interruption like client calling and asking why his mail is not coming through might take you out of flow for 2 minutes but might be that it takes next 2 hours to get back. and they are saying that if developer has few that kind of interruptions per day then it's not very productive. he is basically working 10 minutes.

I am not the originator of this research. but I have witnessed something similar myself. I just remember how frustrating it was when I used to get some calls that I needed to act upon, how it interrupted the state called “flow” and how hard it was to focus back.

* The book suggests that autotelics may experience flow “more easily and more often”. It notes that autotelics are not “self-centered”. Also that they engage in activities for “intrinsic reasons”. What do the latter two points mean, exactly, in this context?

For what it's worth, I don't know if I'm an autotelic or not. Possibly. I can't comment on the “self centered” or “intrinsic reasons” points without better definitions. But I'm intensely curious and remarkably persistent.

Note to Michael Bonetto of Hoge Fenton: If you happen to read this, perhaps you understand the lawful and appropriate implications of the preceding paragraph. I'm starting to understand them myself. I know now that I'm supposed to find out how this was possible. What you've done so casually; like a boy crushing an insect simply because he's bored and he can. I'll write about it. My own books will proceed.

* The line which states that “All programmers are engineers at heart” strikes me as trite. Not criticizing the point but tweaks to the wording might help.

* Another part says that “relentlessly hunting down bugs is a source of great pride for most programmers”. Is it actually about pride for engineers who spend much of their time in flow?

My code has been called “f*cking beautiful”. I'm amused by that and I do take pride in the code. But none of that was in my head originally.

The code existed, somewhere; perhaps embedded in the Implicate Order. It was my task to move it from there to the online world and to preserve its original structure as I did so. Removing flaws or, better, avoiding them to begin with was part of the process.

* One paragraph states: “It could be argued that programmers are very selfless people”. Sure. We're angels sent to relieve the suffering of a world that cries out for the selfless compassion we're known for :P

The point you're addressing here is important in general, of course. Probably needs a book of its own. I'd add a bit more here and fill in minor gaps related to context. If it matters, for the purposes of the current discussion, that programmers are “selfless” or not, why does it matter? This may be clear to others but I missed it.

* The book states: “Yes, flow is indeed much easier to achieve in the evening.” Is it? Flow is easier to achieve when conditions are right. Not in the evening per se though for some people the conditions are right at that time. The text acknowledges this, to some extent, in the same paragraph. But the thesis, which is what this part seems to be getting down to, isn't clear to me.