bwoj

A few years ago, I was tech lead on a team doing the software for IPTV settop boxes. We were trying to grow the team out and not getting many good candidates for the position.

At one point the best candidate we had was a 60+ year old engineer with a background in compiler development. The skills he demonstrated on whiteboard coding and answering technical questions were not great but acceptable and we figured he should be able to transfer his knowledge to a new line of work.

When he started working he struggled to adapt. He had some health problems that included an organ transplant. After a few months in the role, the stress began to cause his body to reject the transplant.

It's clearl that hiring an older worker can have problems you won't likely see an a 20 year old. If I had to do it again, I would still give this candidate the chance. Every time.

I've been reasonably happy with a laptop I've had running Windows 7. Then it stealth-updated itself to Windows 10. I turned off most of the ads, but the lock screen still had ads. I had to turn of some service with an incongruous name to kill those but Cortana still shows up on the lock screen telling me to talk to it. Like I'm going to do that?

Also, the start menu is all fubared. I end up using search from the start menu, which works but is really slow. I'll get the search box and type something into it and it's 30 seconds to a minute before my text shows up there, usually missing the first 2-3 characters I typed... but not always.

Microsoft needs to have a good hard look at why they had so much trouble moving people off of XP. It's like they hit an inflection point there with the least amount of suckage.

To my recollection, the worst performer was parsing all of the QML at startup. This did not impact us at first, but as we grew the QML portion it went from a noticeable delay at startup to an unacceptable delay. It was something on the order of 10-30 seconds (on rather high-powered workstations to boot) to parse all of the QML files for what amounted to less than a dozen UI screens.

On my last project we started an effort to redo our QWidget implemented UI with QML. The QML version was really slow, we actually ended up buying a commercial license to get access to a QML compiler just to speed things up. And that was for desktop, I'd expect it to be even worse for mobile. Integrating the QML components with the QWidget components was especially buggy. For a 100% QML project this would be less of a problem.

Interfacing C++ to QML is clearly not a priority in the design of the whole system. You can do slots/signals or you can register C++ objects into the QML namespace. Something along the lines of this tutorial: http://doc.qt.io/qt-5/qtqml-tutorials-extending-qml-example....

Overall, I find the whole QML environment to be disappointing and I don't plan to use it again until it becomes more mature.

From 2015.

Poker analogy: the nut is the one card that forms the best possible hand out of the shared cards on the table. Having the nut card in the hole means you have it in your hidden cards. When you're in this position, you know you're going to win the hand but the other players do not and your goal is to get them to bid as much as possible on the hand without tipping them off that you know you will win it.

The barrier to entry in the trades isn't the difficulty of the work. If you trained 1000 programmers for six months, a good number of them would be competent, but none of them would be able to get licensed. Every single one of them would need to work as an apprentice to a licensed plumber as part of the licensing requirements.

On the flip side, all you need to do to get a job programming is an internet connection and the desire to learn it. Anyone can teach themselves and if you can code enough BS on a whiteboard, somebody will hire you.

For most people that hew to the teachings of the book, understanding the proper context involves a religious authority telling them which parts of the book matter and which ones to ignore because they don't matter any more. I would like for a divinely inspired book of ageless wisdom to not be so subject to the whims of interpretation.

Of course the super-rich are going to get coddled. If you are in a position of influence they can throw $100,000 to a million dollars your way to make sure you enact the policies they want. This can be in the form of consulting gigs or speaking fees or what have you.

Point is, the money is literally chump change to them.

Not sure why everyone is downvoting. You may not go on a list, but you could be targeted by the FBI if they can produce "probable cause"

http://www.thelastamericanvagabond.com/constitutional-rights...

I deplore the practice of publishing papers without a date. This could have been written any time between 2012 and last week based on the sources referenced.

I worked for a company that went public at $18/share in 2000. During the lockup period the price of the stock went as high as $202/share. Over the next two years, the price trended downwards to around $20/share.

Pre-IPO employees were encouraged to pay for shared before they vested. The idea here is that you can hold those options for 5 years and get capital gains rates on that appreciation which for small companies was 10%. I.E, you pay now, shares vest later. According to the AMT, you will owe taxes on those shares equal to the market price when they become yours minus what you paid for them. That is, when the stock vests. Not when you pay for it, and not when you sell it.

So you can buy 1000 pre ipo shares for $1 each. Company goes public hits $100/share. You think it's going higher so you hold. Shares drop to $10. Now you're in a pickle. You owe taxes on 1000 shares * $99 of gain. But you're only sitting on 1000 shares * $9 of gain. When somebody finds themselves in this situation, they must sell those shares before that tax year ends, which means you're now paying income taxes instead. If your tax year has ended you are out of luck.

The one thing that stops this from being a real problem for most founders is the IRS 83(b) form, which is to notify the IRS that you want to recognize the income associated with your option when you buy it as opposed to the default which is when it vests. Why doesn't everyone file their 83(b)? Clearly, the risk here is too complicated for many to understand and it's a very unusual situation to arise.

Here is the story of how our CFO(!) at that company ran into this exact problem to the tune of $316,040 tax liability for shares he bought with money borrowed from the company(!): https://www.washingtonpost.com/archive/business/2000/07/02/k...

Some references: https://www.nceo.org/articles/stock-options-alternative-mini... https://blog.wealthfront.com/always-file-your-83b/

Nope you're still liable for infringement. It does help you avoid the treble damages for "willful infringement."

This isn't quite so much bypassing the OS as it is redefining the boundary of the privileged space to not include the network traffic. This lets your filtering application get the network packets directly without having to copy them out of kernel space and into user space. This is exactly the same technique all high performance network devices follow presently. The ones that aren't doing it in userspace, are doing it in some sort of RTOS that doesn't even have protected memory spaces.

The source here is CEO of a company trying to sell content protection solutions for the web.

Original post, with working links: http://blog.docker.io/2013/06/create-light-weight-docker-con...