- Install updates
- Run AV software
- Run Zero Day malware
2022/04/15
Back to work!
2022/04/14
Insider trading and the unlevel market
Reading through Is the Stock Market Rigged? I get to the part about Mississippi College School of Law professor John Anderson. To my mind, his opinions smack of an academic who has been immersed in their field a little too long.
Of course, his opinions may be more nuanced than the article suggests. According to the article's author, Liam Vaughn, Prof. Anderson believes insider trading should largely be legal, because they are making the markets function better. Better for whom? Would they still have to disclose their trades? Where would we draw a distinction between "legal" insider trading and price manipulation? Given the wealth and the quantity of stock controlled by executives, price manipulation would be easy to implement. Or should that be legal as well, to release government from the burden of regulating it? I could see this becoming quite the side hustle for a lot of executives, actively shoving prices around to get another 20-30% annual return on their income, and improve "market efficiency".
Within the scope of the article, insider trading sounds like a near-victimless crime, with the person taking the other side of the trade out a few dollars per share, at most. But that's a very narrow focus. The perception that executives willfully take advantage of insider knowledge undermines confidence in the market as a whole. This undermining could, as article does point out, be driving interest in cryptocurrency, and is definitely a driver in the meme stock trend.
Anderson is also quoted as saying “The whole reason people come to the market is because they think they have better information, better understanding than their counterparties.” Which seems like a phenomenally shallow view of the average retail investor, who may be buying stocks on impulse, through a mutual fund in their IRA, a "hot tip" on Reddit, or by scouring a website like Morningstar, but who is definitely not going to the market thinking they have better information than everyone they're trading against.
Personally I think the practice of paying executives in stock grants and options has a corrupting influence, and is detrimental to the long-term health of both the companies and the country. This focuses execs on increasing shareholder return at any cost. If we want executives to have skin in the game, let them get it like the majority of their employees -- have the stock go into a retirement fund and they can't draw on it without paying huge penalties prior to actual retirement. Nor should they be allowed to borrow against that fund without paying significant penalties or taxes. And in the meantime, they can earn a modest salary (at least modest by today's standards).
Random thoughts
How stoopid izzat? He sticks his gum onna unnerside of a glass table.
The woman kept hooting and hollering through the entire concert. I hadn't heard a racket like that since the neighbor's great dane passed a kidney stone.
"Guysa" for the fellows who are smart enough to be in Mensa, but aren't stuck up about it.
To walk while talking
Yet no one is there -- insane?
No, just a cell phone.
Characters for the Novel "Not til Death Did We Part"
Felice -- Fluff romance novel writer
Roger -- Historical fiction writer, obsessed with Jimmy Hoffa
Sandy -- Writes hard sci-fi that never makes sense
Tom -- Writer of murder mysteries that are usually dead on arrival
Martha -- Writes poetry so bad, she can't find a poetry group that will admit her
Capitalism: an economic system that generates material wealth while causing catastrophic ecological damage.
Communism: an economic system that generates abject poverty while causing catastrophic ecological damage.
The "Maybe Good Enough Sort Algorithm" An algorithm that provides an approximate ordering, this algorithm getint about 90% of the elements into some sort (haha) of order. Has the dubious advantage of providing a "good enough" result quickly.
iPad Wands or Wii Sticks Small rods that give positional feedback. With five, there'd be one for each finger. Okay, K'nect may be a better answer.
http://all-story.com
http://www.pshares.org
There are few things you can't do in C++. Writing correct code is one of them.
Maybe not stupid product idea: a trash chute for apartment buildings that can identify items on the fly (haha) and bat them into an appropriate bin for recycling, composting or landfill.
2020/09/13
Software and the Doggie Doo Effect
DDSM (Doggie-doo Software Management)
The unpleasant and unintended stickiness of legacy software.
Example:
Manager: "Jim, you were the last person to work on X. I'm assigning this bug to you."
Jim: "This stinks!"
Does Microsoft Exist in a World Without People?
The Microsoft Windows lock screen features an ever-shifting series of landscapes, sometimes pastoral, sometimes of adventurous heights, or even famous landmarks (Stonehenge recently came up for me) but all of them have one thing in common: no people.
I don't know why. This could be intentional and they edit them out, perhaps worrying that people would be "disturbed" to see other people on their PC when they were logging in. It could be some massive self-selection process where early on, people just trained the AI serving these up that people-less pictures are preferable. Or perhaps that AI is sending the subtle message, "the world is better without you".
2018/12/16
Why Merging Software Products is Harder Than Expected
At one of my previous companies, something similar unfolded. The company had two tiers of products for the same market. One was high-end and very expensive, the other was the lower-cost alternative. Both were very mature products and as you might expect, over time functionality converged a bit, as the high-end product extended into features suitable for smaller customers, while the low-end product expanded its offering. Each product had its own strengths and weaknesses.
Management noticed that and said, "hey, these two products do a lot of the same things, why not combine them and get the best of both worlds?" They filled a chart board with post-its showing the commonalities between the products. Each post-it contained words like "generates reports", and "computes portfolio balances". Never mind that each post-it encapsulated big piles of bespoke code that had only ever talked to post-its within the same product.
This is a bit like some big manufacturer saying,"we build trains, and we build buses, and they both do similar things -- moving people and stuff around. The great thing about a bus is that it can go anywhere there is a street. Trains can only go where the tracks have been laid, but they have a much greater capacity, better energy efficiency, and can be customized out of modular components. What if we take the best of a bus and the best of a train, and put them together? We change out the wheels and we have a tra-bus that can go anywhere! And the bus windows are much nicer, they're bigger and people can open them. Let's put those on."
And so it goes, until you have an incredibly ugly train-like thing built on a bus frame, that isn't street legal, that can't use existing modules (railcars) and now it needs more engines and better brakes, and so on.
As incredibly bad as this idea is in (vehicular) hardware, it's even worse in software; with these bu-train monstrosities, the problems of connecting the disparate parts are physical and easy to visualize.
In software, its too easy to lose sight of how parts fit together, and the possibilities are unbounded (blocking API, async API, restful API, redirected I/O, mapped memory, named pipes, sockets, protocols built on sockets, databases, data files, etc). Also, the parts can be written in entirely different languages that have trouble talking to each other. It doesn't even have to be different languages to be hard. Combining C++ written for Windows with C++ written for any other operating system can be insanely difficult. The challenges of integrating software products are enormous, and easy to grossly underestimate if you just break the product down into a bunch of functional boxes scribbled on post-its and say "hey, most of these boxes do the same thing!" If you see management doing something like that, its either time to speak up, or time to update your LinkedIn profile.
Inverting the emulation stack as a thought exercise
Today I'm working on a Windows machine with a 64-bit, 4 core processor clocking 2.8 Ghz, and accessing... well, its Moore's Law in action.
Would it be possible to write a AMD64 emulator on the 6800? I don't think it can be done within the RAM of the processor. Given the complexity of a modern core, more code may be needed to emulate the instruction set than will fit in 64K. Restricting the code to a subset (off-boarding floating point, for example) might help it squeak by, and we would not implement many internal features such as instruction reordering or prefetch.
So.. if it takes a couple hundred 6800 instructions to emulate one x64 instruction (on average) and the 6800 runs at 2 MHz, and emulation doesn't require any I/O to a file system, then the emulated x64 would be executing about 5K x64 instructions a second, or "only" a 400K to 1 slowdown.