Hacker Newsnew | past | comments | ask | show | jobs | submit | ldx1024's commentslogin

"Although the standard is a little more complicated..."

If you have ever read the software control category definitions in MIL-STD-882E you know that the definitions that this blog author gives are very much his interpretation. The actual definitions in 882E are a god awful mess. Multiple contradictory definitions provided for the same category. Additional parenthetical statements that are intended to clarify, but just muddy the picture further. Yikes...


"Haunted house" themed halloween amusement area, I assume from skimming the article



I was just thinking about this. Exposure from a short is theoretically limitless. Some sort of derivative would be a better approach? Asking for a financially clueless friend.


All I have to say is good luck out competing the big firms!


Buy puts


The financially illiterate don't understand that "going short" is not the simple reverse of "going long" and that there are more difficulties involved with borrowing stocks to short or in buying puts. Well, puts are easy to buy, at least, but the manner in which they decay makes it hard to win with that strategy, harder, in fact, than buying calls to go long. But yes, you can technically buy puts. You can also play Powerball.


If you buy a put option, you can’t lose more than you put in. The problem is still one of timing things right.

Check out /r/wallstreetbets for expert advice on this. /s


NDAIPF


Check out the University of Massachusetts Dartmouth campus, too, about 60 miles south of Boston


Software is only subject to entropy when you touch it. In most practical cases these days not being able to "improve" the software is a feature, not a bug.


I have a hard time identifying with this. The premise seems to be that the worker is just a passive participant in the system, literally a ping pong ball on a galton board. If the end state isn't what is desired the problem is with the board not the balls. This in fact may be true in the large, but that is the same as saying that management systems and processes are for people that need management systems and processes, reliably producing mediocre results. There is definite tension in accepting that this mediocrity is practically inevitable if anything is going to be done at scale.


If you treat people as overly simple machines you might as well mechanise that part of the process.

Human workers have hand skill, learning, intelligence, wisdom, introspection, communication, colour and pattern recognition all of which are not being utilised making the job repetitive and unfulfilling.

Then the threat of firing based on a random metric - this would create a culture of fear and one would expect a high turnover of any ‘good’ employees.

I agree this would be a horrible place to work.

Which is the genius of the allegory - how the wrong metric can make efficiency and progress impossible.

Of course even a good metric becomes corrupted according to Goodhart's law:

“ When a metric becomes a target it ceases to be a good metric because people will seek to game it.”

‘The Wire’ remains a salutary lesson on how all stats when tied to pay and promotion will get ‘juked’.

A metric can measure nothing but random chance ( there is always some randomness that is rarely accounted for ) - this makes management impossible and workers disempowered.

Even with good stats there are too few Baysians vs Frequentists in corporate numerical analysis.

In terms of the company in this analogy a useful exercise is to imagine how to improve things.

An immediate solution could be to allow the workers to make multiple sequential draws and to discuss what percentage of red beads constitutes a good draw and discard and resample if more red beads than that.

Let workers share their best practices and it may be that there is a subtle skill that can be learnt about how one wields the paddle in the box of beads to steer it away from red clusters.

Or divide and conquer and take fewer beads and allow the workers to discard all red beads, then combine the pure samples and batch up to correct size.


I know next to nothing on the subject, but I won't let that stop me :) If this has been sitting here for three hours with no response I might as well pipe in...

Reddit link discussing topic:

https://www.reddit.com/r/androiddev/comments/17w3pgz/google_...

If you think the app might make some real money you might want to think about registering an account with a business name and virtual mailbox address. I didn't read the whole thread above, but that comes up early in the thread as one option.


Lol thanks for the response. I have unfortunately gone over this thread and others a ton, and also reached out to google, and they seem to not allow PO Boxes. There is a way to buy a physical mailbox that some people have mentioned and may try that.. they pull the address from the payment profile section or ur account though so don't know if they will allow using a mailbox address there..


Virtual mailbox is not allowed unless you somehow trick D&B into accepting it. But they try their best to block them all.


Makes one think that the Ada programming language will be involved...


Wow, this is the first time I heard about Ada Language


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: