Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror
DEAL: For $25 - Add A Second Phone Number To Your Smartphone for life! Use promo code SLASHDOT25. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. Check out the new SourceForge HTML5 Internet speed test! ×

Comment Re:Not a struggle (Score 1) 79

This. I mean, you should be able to invest that in the stock market and average at least $8 million per year, permanently, allowing enough extra money to compensate for inflation. That's enough for a team of at least 20 engineers plus renting space for them to work, equipment costs, health insurance, etc. So barring the website being insanely complex, you should literally be able to run it on that without even touching the principal, even without bringing in a penny of revenue. What the heck are these people doing with all that money?

Comment Re:US Capital Reinvestment Problem (Score 1) 79

True, though there are thresholds below which expansion makes no sense. Say I have a bookstore. I have ten employees and overlap them to keep the store open during reasonable business hours.

  • Adding five more employees is unlikely to provide any additional ROI unless I can claim to be the only 24-hour bookstore in the region, and only then if there's actually a group of people who wake up at three in the morning, think to themselves, "I need to read something to help me get to sleep", then put on their clothes, drive to a bookstore, buy a book, drive home, take off their clothes, curl up, and read the book.
  • Adding ten more employees would be enough to open up a second bookstore in a nearby town. Assuming there are enough customers to keep both businesses alive, then yes, given available capital, there's more work to be done.

In big businesses, the interesting thresholds tend to be even bigger and more dependent on things other than available capital. You have a lot of opportunities for bringing in a new person in various parts of the company as workload increases over time, of course, but the really interesting, rapid growth happens when the company decides that they want to go after a new market segment, which means they have to ramp up their staff fairly dramatically. That requires more than just capital; it requires big ideas and a reasonable probability of making enough money to make it worth the effort.

That's why even though Apple's U.S. profits alone could cover the cost of hiring on the order of 700,000 full-time software engineers, they have on the order of one percent of that number. So probably only about one or two percent of their revenue goes into staffing (ignoring C*O and VP bonuses). Even if you double or triple that number to cover the cost of renting or building office spaces, assuming you ignore the occasional massively over-budget project like the spaceship, total employee costs still probably fall down in the single-digit range percentage-wise. In other words, if they needed more people, they would easily be able to afford many more people, so bringing more money into the U.S. won't change their hiring at all. This tends to be true for all sufficiently large businesses. In other words, there's a threshold of capitalization beyond which adding more money won't result in more jobs.

The bottom line is that if you want to increase the number of available jobs, the best way is to raise taxes on big businesses and use that to offset a reduction in taxes on smaller businesses. Those smaller businesses still have room to grow, and every dollar that they pay in taxes is a dollar that they can't pay their employees; for bigger businesses, every dollar they pay in taxes is just a dollar that they can't pay their shareholders, which although certainly beneficial, does not create jobs.

Comment Re:The main problem (Score 4, Interesting) 79

Of course, a big part of the problem is that in the 1970s, California enacted a property tax scheme that is perfectly designed to limit homeowners' ability to move. By making property taxes be based solely on the purchase price instead of on the actual value of the home, people would pay dramatically more in property taxes every year if they sell one house and buy a second one even if they break even on the deal.

Prop 13 drastically skews the proportion of renters to owners by forcing people to rent out their old place so they can afford the rent on a new place instead of selling and buying. It also discourages new people from entering the market by making them pay the bulk of the cost of goods and services while folks who have been there for a few years pay proportionally less. The result is one of the most screwed up real estate markets anywhere in the world.

(BTW, Sunnyvale mobile home parks are only ~$1k per month and only maybe $50–75k to buy an old house and move it out of the way, plus the cost of whatever you move in. That extra $1,500 per month + $75k is the Google tax you pay for living five minutes closer to work.)

Another part of the problem is that the Bay Area lacks a proper region-wide planning commission with authority to regulate zoning across the various cities. So you have places like Menlo Park, where the only housing is private estates for the rich C*Os, with lots of businesses out near the shore where land is cheap (because it smells of rotting fish), and you have Gilroy and Morgan Hill that are almost entirely housing, with few businesses.

IMO, what we really need is to have some government entity that slowly converts business-use land in the South Bay to residential use and says "No" whenever big companies say that they want to expand their presence in the South Bay, encouraging them to build satellite offices farther south instead. And offer tax incentives to locate new businesses outside the SF/Peninsula/South Bay area. Adding more businesses farther south would increase the reverse commute traffic and reduce the primary commute proportionally, and opening up more farmland to development would go a long way towards reducing the cost of housing as well.

Unfortunately, that's unlikely to happen unless there's a single management agency that has some authority across all the different administrative districts. Right now, each city wants to get its share of the tax revenue from new businesses, and they mostly don't care about the clustering problems that result from it. Nobody is taking a bird's eye view of the problem, or if they are, they don't have the authority to do anything about it.

Comment Re:Inherent contradictions within leftist ideals. (Score 1) 304

Greece, as best I understand it, is screwed up because the government paid for it without actually having the revenue to pay for it. That makes them far more like the modern borrow-and-spend Republicans than the tax-and-spend progressives. When, over a five-year period, a country's tax revenue increases by 31% and government spending increases by 87%, you're going to have a serious increase in your national debt. The United states solves this by devaluing its currency. Unfortunately, the Greeks are part of the Eurozone, and thus are limited in how much currency they can print each year, which means they can't just print more money to avoid becoming crippled by their national debt.

Of course, to make matters worse, their national debt is so huge relative to their GDP that it probably wouldn't help even if they could print money. Even in relatively good times, Greece was borrowing over 8% of their GDP every year. That's simply unsustainable. As a result, while U.S. states have debts that are on the order of a third to half their GDP, Greece has debt that is on the order of double their GDP. Imagine if the state of California took on a third of the national debt by itself, and you're in the ballpark. Nobody in the U.S. government—even the most socialist progressives who advocate a base income—are crazy enough to borrow that kind of money, I don't think.

But a bigger problem is not the amount of spending, but rather the types of spending that the Greek government has done. Instead of building infrastructure that would actually benefit them financially (e.g. factories), they spent frivolously on things like a giant sports venue for the 2004 Olympics that didn't cover its costs and that they couldn't afford to actually maintain afterwards. Their social security system is or was broken, with such fascinating flaws as paying out pensions to single female children of dead retirees. The state airline was a giant money pit for many years. And their military spending at the start of the crisis bordered on insanity (sound Republican enough for you?) at something like 7% of their GDP—proportionally more than the U.S. spent while fighting two wars.

No, the Greek government is a prime example of what happens when Reagan-Republican-style borrow-and-spend budgets get out of control and are not tempered by true fiscal conservatives insisting on balanced budgets and rainy day funds and so on. It is the polar opposite of progressive ways of handling budgeting (which, if they got out of control, would result in a tax rate that's so high that the people themselves would demand cuts in spending).

Comment Re:Inherent contradictions within leftist ideals. (Score 2) 304

Here's what happened in about 150 years under "conservative" US government policies:

Grew from small, isolated, breakaway country to the richest, most powerful country on the planet, with the highest standard of living.

Here's what happened under "liberal" government policies:

  • Declared our independence from Great Britain in the first place.

You have the right to be on Slashdot and argue about which ideology is better because of liberal policies.

Along the way, freed slaves and saw life expectancy become the highest in the world.

Lincoln was most assuredly not conservative. Republican, yes. Conservative, no. His policies resembled those of modern progressives more than modern conservatives, though even that is something of a stretch, because unlike 99% of modern politicians, Lincoln was actually a respectable statesman.

Contrast to what happened in "progressive"/socialist/liberal nations such as Venezuela, Greece, and the Soviet Union.

Progressive != socialist != liberal.

Additionally, Greece's problems stemmed from government overspending without enough taxation to cover the expenses. That's more similar to what Republicans do today than Democrats. And both Venezuela and Russia had problems where a few people at the top of the party essentially lived in luxury while the poor starved, which makes it more like a caste system than true socialism.

Besides, essentially zero modern progressives view socialism as the be-all and end-all of public policy, but rather as a useful tool to use in limited ways for the public good. That's radically different from a country that attempts to use pure socialism as its sole policy (which is exactly as foolish as using pure capitalism as the sole public policy).

Comment Re:OP fired because of this article (Score 2) 222

Legally, it's a grey area. If your employment contract has morality clauses, for example, you can be punished for things done outside of work. However, usually that is limited to situations where your contract explicitly states it, which usually happens when working for religious institutions (or, occasionally, schools). You can also be fired for actions that reflect badly on your company, but that assumes that A. people know the author works for that company, and B. they have reason to somehow connect the two. And of course, in at-will states, your employment can be potentially terminated for any reason, though in many, the implied covenant of good faith might give the author grounds to argue that this was without cause, done out of malice arising out of personal embarrassment on the part of the management team.

The bottom line would be that the author should contact a lawyer who regularly deals with employment law in that part of the country, because whether he has a case or not is highly dependent on where the author is located, and I'm pretty sure it won't be open-and-shut no matter where the author lives. However, the fact that the author has not revealed where he works does open the opportunity for the lawyer to point out that bringing this to court will cast their company in a very bad light publicly, whereas an out-of-court settlement for... say ten years' salary will not. Depending on how terrified the company is, such (entirely legal) blackmail might actually be more effective than bringing a suit.

Comment No problem (Score 2) 46

You can have that however you have to accept a few things:

1) Costs are going to go way up. You aren't going to pay $50 or $100 for a software package, it'll be 5 or 6 figures. You'll be paying for all the additional testing, certification, and risk.

2) You won't get new stuff. Everything you use will be old tech. You'll be 5-10 years out of date because of the additional time needed to test and prove things. When a new chip or whatever comes on the market it'll be a good bit of time before it has undergone all the validation it needs to be ready for such a critical use.

3) You will not be permitted to modify anything. You will sign a contract (a real paper one) up front that will specify what you can do with the solution, and what environment it must be run in. Every component will have to be certified, all software on the system, the system itself, any systems it connects to, etc. No changes on your part will be permitted, everything will have to be regression tested and verified before any change is made.

If you are ok with that, then off you go! The way I know this is how it goes is that we have shit like this, we have critical systems out there and this is the kind of shit they go through. They are expensive, inflexible, and out of date compared to the latest mass market shit. If you look at the computers that control a fighter plane or the like you'll be amazed at how "dated" they are. Well they are that way because development took a long time and once they are developed, they continue to be used, they aren't changed often.

Now if that's not ok, if you want the free wheeling environment we have now where you can buy new tech when you like, put things together in any configuration, and run whatever you want that's cool, but accept that means problems will happen. You cannot have it both ways.

Oh and also with that critical stuff:

4) There will be no FOSS. If there's liability for losses, nobody will be willing to freely distribute their work. They aren't going to accept liability for no payment, and aren't going to accept that if their code was used by someone else they might be liable.

User Journal

Journal Journal: Gone Again!

As always, if slashdot has borked the text, just go here.
She was gone again, shortly before my elderly cat died. I refer to my muse, of course.
I looked everywhere I could think of, to no avail. Stolen again? I went for a walk, on the lookout for that aged black aged Lincoln with that blonde and that brun

Comment Re:Yes, but... (Score 1) 222

In my experience, what makes it chaotic is the vast expanse of code that you didn't write personally. I've seen big chunks of functionality have to be completely rewritten because even major frameworks from major companies like Apple sometimes have bugs that are showstoppers when used in some way that the original author didn't expect. Most people normally assume that external dependencies already work when estimating, because after all, those are major frameworks written by major companies with testing resources.

Now extend that to code written by random engineers with limited testing resources. Normally, you assume that your internal code works, because after all, people are using it every day. But what happens when there's an edge case you didn't notice? If it isn't a crash, a bug in a suitably complex app often isn't easy to track down, and even when it is a crash, it might be some subtle multithreading race condition that can be utter misery to debug. And the larger the app, the more opportunities for untested code paths to suddenly find themselves on the hot path. This is why estimating is hard; you aren't just estimating how long it will take to get your code working; you're also estimating how long it will take you to fix everybody else's mess.

Comment Re:Leftists are learning about pushing people too (Score 1) 272

One prominent example is minimum wage regulations. While the intent behind these may have been good, what they've ended up becoming are huge burdens to businesses that are already on the brink. It's not economically viable for a business to pay somebody far more than the value they're providing. What is the end result? Fewer jobs, and a lot more focus on automating away low-end jobs. This actually leaves people worse off than they were before the minimum wage regulations were put into place!

That's a very naïve view of reality. For every business that's on the brink, there are hundreds that are doing well, and many that are turning record profits. A business that cannot afford to pay its employees a living wage is almost certainly doomed anyway, so allowing it to pay a less than a living wage is just delaying the inevitable slightly. The business will fail. Let it fail.

Keeping a business on life support by letting it pay a subminimum wage doesn't help anyone in the long term, and doesn't help very many people even in the short term. But allowing businesses to pay a subminimum wage does hurt people who work for all those other companies that actually are profitable, because given the opportunity to pay their employees less, they will do so.

More to the point, if that is the only business providing jobs in a particular community, then that community is doomed. Keeping the business alive a little longer by depressing wages just encourages people to stay in the doomed community and make less and less money, thus making them less and less able to afford to move to a community that isn't doomed. So continuing to pay those employees a wage actually ends up hurting those employees more than it helps, at least in the aggregate, though the individual employees might not believe it at the time.

Slashdot Top Deals

Sendmail may be safely run set-user-id to root. -- Eric Allman, "Sendmail Installation Guide"

Working...