And certainly there are other cases where OSS blazes the trail. But copycat software gets a hall pass when it you get to download it for free? Or is your post just a different iteration on the iOS/Android fanboy-ism?
382 karma · joined August 19, 2011
And certainly there are other cases where OSS blazes the trail. But copycat software gets a hall pass when it you get to download it for free? Or is your post just a different iteration on the iOS/Android fanboy-ism?
Whereas with smaller companies where you can pretty much do carte blanche ("install whatever software you need on your PC as long as it doesn't drain our Comcast business internet"), working from home would probably be looked down upon.
If you start with $100 and you want to make $150 you need to make a 50% return. If your $100 drops to $50 you need to make a 100% return just to get back where you started, let alone where you want to end up at $150.
Learn to effectively communicate and then communicate with your peers. You'll never know what you don't know unless you discover it (and there are only so many hours in a day), or you learn from other people. And you'll have an easier time trying to articulate your visions when you can communicate them effectively.
Don't worry about how good other people are. In fact, it's good to surround yourself with people that are more talented than you are, because it's easier to learn from them. Try to surround yourself with people smarter than you are. This is a lot easier if you contribute heavily to OSS or work in a product-focused group or company. It's pretty easy to let your skill set stagnate if your primary responsibilities are writing internal-use-only software.
Then you can take it one step further: If you indebted in cash or cash equivalents to buy productive assets you get to double-dip: your debt gets reduced by inflation and your productive assets aren't any less productive and their income/growth will adjust. Your overall buying power will greatly increase.
In any good development shop you make a change, your CI server picks it up, builds it, and creates a release candidate you deploy. Every change should be checked into source control and built by your automated build bot.
At that point the difference between changing an annotation and an XML configuration file should be moot. I'd think the annotation would be easier because you can still mess up the syntax of the XML file pretty easy (e.g. "Can you change the blahblah label to System & such?" That ampersand will hose your system when you get it to production).
This is probably something the FDA should do anyway. Generic drug makers can look at a drug's signature, but there are so many other variables that can affect how a drug performs (quality control of the factory, quality of ingredients, recipe, procedure, etc.) that the FDA should require generic makers to go through the same testing process because they're different drugs.
The generic drug makers will have less overall expenses to bring a new drug to market (because someone already figured out a particular protein sequence that works in XYZ manner), but the original inventor will have time to milk the market as the first-to-market, encouraging innovation, and we can still get rid of our awful mess of a patent system.
Generally if you've built up a whole system (like the patent system), and it's really only beneficial for a select few (pharma), then maybe it'd be better to design a different system just for them (like the one proposed above) and don't make everyone else suffer the consequences.
EBay's an open market with buyers and sellers and people just take it for granted they'll get screwed by EBay/PayPal at some point in their lives. I understand that there is probably more at stake in the NASDAQ than on EBay, but their Risk/Compliance department should have advised the principles of his fund to hold some capital off to the side for a situation like this.
We never have enough. The march of technology should be relentless. I for one can't wait to see how the guys at Intel/AMD/ARM or someone out of left field comes up with a way to get around this.
If I'm well paid and satisfied with my current job then I'll make sure to get a good night sleep and be ready the next day to do a good job. If I'm unhappy or think I could be making more then I'll either do work on the side or spend more time working on my resume and interviewing for a better job. If I think my career doesn't have much potential then I'll really spend a lot of time outside of work trying to switch careers.
If you want teachers to do a good job, hire talented people and pay them accordingly. If you want a McDonald's like education system where a handful of chefs come up with bland but easily executable recipes then we can go down that path too. Just don't be surprised when your kids are switching careers from fry-vat guy to third grade teacher. And don't be surprised when the talented teachers see it as a stepping stone and get the heck out of there.
The array/list can be pre-allocated to the size you need and have good cache locality and minimal container overhead -- the linked list will have the overhead of the pointer to the next node (2x for a doubly-linked list) + the type descriptor (if you're using a language like c#, java, python, etc.) per node and data located all over the heap with cache misses everywhere.
<sameCondescendingToneAsParent> If I was asked during an interview why inserting things in a linked list is faster that [sic] inserting things into an array, and I provided an answer that made him blankly stare back at me, would I want to take the job? </sameCondescendingToneAsParent>
Perhaps you're getting a guy switching careers or fields of expertise (web -> system or accounting -> embedded), or someone that just has that gap in their knowledge, or someone that's just having a plain ol' brainfart at that point in time. No need to be as rude as I responded in my third paragraph.
I've thought about ratcheting it down to 15 based on stuff I've read, but unfortunately that particular failure metric can only be set as low as the class-level in the latest version. The next version (4.0) will have the ability to set the threshold at the method level.
In any case, I'd rather have a handful of places in the code where someone has to do something goofy to work around that metric rather than accidentally allow the whole project's complexity to creep up as time goes on.
Well you sure do talk the talk. ;)
Ba-dum---Crash!
You're already making the judgement that the work he's doing isn't valuable, finish it up and judge what he should do.
Stocks and bonds are "fungible" meaning that they can be traded on any exchange that will let them, or even via private agreement which is called Over The Counter (OTC).
Futures are not fungible, so contracts that are traded have to be traded on the same exchange where you got them. The main reason for this is that each futures has a contract specification that would need to be the same across exchanges to be fungible: e.g. one contract of light-sweet crude oil is X U.S. gallons of oil at Y quality... The other reason for this is that once the contract has been traded the exchange (or your broker) assumes the counterparty risk if you or your counterpart default on the contract -- so keeping it all on a single exchange helps everyone keep track who sold what to who.
Currencies are the worst: there is no central market. It's all inter-bank agreements and probably the lightest regulated of the bunch. Retail customers get hosed because it's absolutely legal for your broker to front-run your order and skim a couple pennies off your trade.
I might borrow this next time I have to give a toast at a wedding or a rehearsal dinner. I don't have to mention to anyone it's career advice... :)
Sidenote: if you're interested in doing the same just go to http://www.getgrandpasfbifile.com/
Fantasy football has a nice rhythm: Peak at your team on Thursdays half-way through the season because of the handful of Thursday night games, adjust your team at lunch on Friday, check your scores on Monday.
At least for casual people. Maybe those hard-core will move to fantasy golf...
When kids are first born they need to eat every 2-3 hours including night-time. And a feeding can take anywhere from 15-45 minutes, with a diaper change per-feeding. If you're in the boat that Jeff or I were in you were very fortunate if your twins were both on the same schedule -- offset schedule twins are exhausting and relentless.
Oh, and 50% of twin births are C-sections and my wife was no exception. So her only jobs for the first six weeks were to recover, breastfeed, pump breast milk, eat, and sleep. Daddy took 6 weeks off work (3 unpaid) and pretty much had to do everything else until my wife recovered from her major abdominal surgery.
Not asking for pity or sympathy. I'm just saying that I don't know how people handle newborn twins without help from friends and family. It would be impossible.
Now that they've just turned a year old I can safely look back and vaguely recall that: Yes it probably took about that much time to take care of the little guys.
Good luck, Jeff!