I have given people more than they've asked for a couple of times (usually if they've asked for something that I know to be under market rate and I don't want them jumping ship in a year). But yeah... as a hiring manager I want to know what your expectation is because that's what I'm going to take into consideration when I compare you against other people I've interviewed.
i.e. Dev A has everything but costs 20% more than Dev B, who I think can pick up everything we need within a year's time. Or, Dev C has claimed to have done all of these different things, but is asking for an amount that is suspiciously low.
If you have only one offer, then that could happen, but it's unlikely if you have more than one offer or at least several interviews (and I would always mention this).
The major problem with the much cheaper taxing of capital gains remains the growing inequality: Of every you dollar you earn through your own labor, you get less (until you pass the max threshold). And this while your capacity of personal labor is clearly somehow limited. On the other hand, people earning one million dollars from capital gains are taxed equally with people who earn one billion.
There are two counterpoints to this. The first is that capital gains taxes tend to be on investments made with income you've earned, so there's already been an income tax. The second is almost all of the uber-rich made their fortunes by growing a small company into a big one, so it's not as though they're already being taxed (through progressive corporate taxes).
There are obvious flaws to this scheme, but it's pretty hard to tax income in a fair way. Some places (notably the EU) favor using a consumption tax instead.
> The first is that capital gains taxes tend to be on investments made with income you've earned, so there's already been an income tax.
I don't really get this counterpoint; isn't everything in the economy a flow of money that has been taxed at a previous point in the flow? If I have $100,000 that I've already paid taxes on, I could invest it in external assets and hope to make capital gains on them; or I could plow it back into my own occupation and use it to generate income (say, by setting up an art studio). Why should I pay more taxes in the second case?
Consider two eBay-painting-seller scenarios. In the first, I buy painting materials, paint paintings, and then sell them on eBay. In the second, I buy existing paintings on eBay that I think are underpriced, and then resell them later for a profit. Why should I pay more taxes in the first case, just because I painted the paintings? In both cases my occupation is basically "selling paintings on eBay", but in one I'm creating new ones and selling them for an income, and in the other I'm flipping existing paintings, making a capital gain. In both cases the starting capital is money I've already paid taxes on. If anything, the first occupation seems like the one policy should encourage, rather than the second, but at the very least I don't see any reason to actively encourage the second version over the first.
The outlays being tax-deductible is the same in both cases: you only pay tax on the gains between what you put in and got out, not on the total revenue. If you spend $100k on art supplies and sell $110k in paintings, you pay taxes on the $10k net profit. Same as if you bought a bond for $100k and sold it for $110k; you only pay taxes on the $10k net gain.
But in the second case, you're taxed at a lower rate, so the tax code appears to want to discourage you from investing your capital in your own work. If you ever find yourself in a situation where you could make a 10% return on capital by putting that capital to work yourself, or could make the same 10% by putting that capital into a passive investment, the tax code promotes the 2nd option.
I think the idea of double taxation is a bogus one. When I get money from an entity or process or by working there is no reason to consider whether or not the source of the money has paid some tax in some context. From the perspective of the person receiving the money the only thing that matters is that you got the money.
I pay income tax. With the money left over, after paying the tax, I buy things. I pay tax on the things I buy even though the money has been taxed, so to speak. Suppose I buy something from the place I work at. The money I'm spending to buy the object has been taxed multiple times and part of that money ends up back in my hands. You just can't realistically distinguish between the myriad ways that money has been previously taxed.
not saying if this is right or wrong, but with dividends at least, they are taxed first at the corporate rate and then again when they are distributed as dividends.
Increases in equity on average, but not in the short term, coincide with accumulation of shareholders equity via retained earnings.
>>
they are taxed first at the corporate rate and then again when they are distributed as dividends.
>>
Really? Well that sucks. What logically should happen is if you receive dividends and the company already paid 30% tax on it, and your personal tax rate is 45%, you should pay only the extra 15% tax. (And it does happen over here in Australia).
Otherwise what you get is that companies, in shareholder's interest, try not to give out so much dividends because they will be taxed twice. Instead they keep the cash to boost the share price so shareholders make capital gains.
You'd ask, what is really the point of buying stock in a company that will never pay dividend in its lifetime?
You'd ask, what is really the point of buying stock in a company that will never pay dividend in its lifetime?
They can distribute profits via share buybacks. Instead of distributing 1% of the companies value as dividends, they can buy back 1% of shares. You then have the option of selling 1% of your shares back (equivalent to taking dividends) or keeping your shares (equivalent to reinvesting dividends).
This only works if you are a big shareholder - if you are a small time player on ETrade, transaction costs will kill this idea.
That's in practice what happens, but it does make for a bit of strangeness from the perspective of fundamental valuations. At least in idealized theory, a stock is worth the time-discounted value of its future dividends plus any terminal liquidation payout (if the company eventually gets sold for cash). A share buyback increases the share of a company that a given stockholder owns, by getting rid of some of the other outstanding shares. That should make the share more valuable, because it's now entitled to a larger percentage of those future earnings... but raising the percentage of future earnings you're entitled to is only valuable if there are any! So either there have to eventually be some dividends or a cash sale, or else we have to abandon that view of valuation as having any tie to future earnings.
"What logically should happen is if you receive dividends and the company already paid 30% tax on it, and your personal tax rate is 45%, you should pay only the extra 15% tax. (And it does happen over here in Australia)."
I was skeptical of this claim but Wikipedia confirms - that's an interesting scheme. It basically eliminates taxation as a decision factor in incorporating a company or not. That's interesting, I never heard of such a construct before, although it's quite obvious.
In most of Western Europe, there are different rates for dividend and income tax. So if you own a company, the company first pays e.g. 20% 'profit tax' on it, and then you pay 25% on the dividends; in the end, roughly coming out to the same marginal highest tax bracket for the income tax.
Great subset, one has to hope people do not read this as "this is how you game the interview process" but rather as "reflect about your idea with these points in mind".
Absolutely. As paul buccheit likes to say, limited life experience + overgeneralization = advice. Take what I'm saying with several grains of salt, and recognize that every interview will be VERY different in tone, style, and content
This is a very big problem: the constant focus on tools and specific technologies instead of looking at the people and their abilities.
A great developer will always be able to pick up a new language/framework/paradigm quickly. So if you plan to have a longer relationship with your hire, you can by all means afford not to check every bullet point regarding technologies. By strictly requiring explicit experience in the fields you are working in, the only thing you really accomplish is to drastically reduce the number of possible applicants.
For example, since Django is still a lot less common than Rails, if you need a Django developer and specifically require Django experience, you will not have an awful lot of candidates. If you broaden your search to anyone with experience with a web framework, you are almost guaranteed to attract some more good candidates. Once you screen those, you pick the best. Best case: he/she was already familiar with Django, congrats to you. Worst case: the dev was not familiar with Django, but still a better fit than ALL the candidates with Django experience. Sounds like win-win for me...
I think us developers all tend to know this. But for some reason most employers still don't get this. Almost all job listings look for candidates with specific experience in technology X, rather than just all around smart and able people. When I am job hunting these types of employers are an immediate turn off for me, but they are by far the majority. I wish we could succeed in convincing employers to look at the bigger picture.
While I agree that you probably miss out on finding a lot of great candidates, there is a significant advantage in finding someone that already knows your chosen platform.
Already knowing the OS and Tools allows a new hire to focus on understanding the business domain quickly. For some companies, that's far more important than raw technical ability.
The "quickly" argument is a strawman, if you plan on having a working relationship that lasts longer than 3 months or so. If you just need someone to upgrade your current Rails 2.3.8 project to 3.0.6 and then move along, by all means get someone with Rails experience.
But if you intend to employ that person longer, the specific experience is of diminishing importance.
That's why I usually try to describe myself as a bard of programming. Pick a language. Pick a framework. I know enough to get started, and I know where to find answers to my questions.
This might be another incarnation of the "Nobody ever gets fired for using IBM" phenomenon. HR are more likely aiming at avoiding errors, and not necessarily hiring the best people possible, if those come at a risk. So you can always say "but he had x years experience with Rails" if the hire doesn't pan out.
A caveat: In creating something, requisite domain knowledge is required. Know where your strengths and experiences are, how to leverage them, and be resourceful enough to obtain new skills. Don't be afraid to seek help.
This is more likely just a publicity stunt to calm down the people, since there are elections coming in several federal states and the reigning party CDU already lost a lot of ground. I would be surprised if anything really changes
Even better is to additionally setup a fake SSHd at port 22, so that port scanners do not even bother keeping on looking for the port and instead use what they suspect to be working
I run it as a dedicated user, on a high port. Port 22 of the router is merely forwarded to the internal high port I use.
Sure, I could chroot the thing as well.
# accept traffic to the normal ssh port
iptables -A INPUT -i eth0 -p tcp --dport 22 -j ACCEPT
# accept traffic on the port kippo is listening on
iptables -A INPUT -i eth0 -p tcp --dport 2222 -j ACCEPT
# direct traffic inbound on port 22 to port 2222
iptables -A PREROUTING -t nat -i eth0 -p tcp --dport 22 -j REDIRECT --to-port 2222
Make sure also to add an ACCEPT rule for traffic to whatever port sshd is actually bound to.
That's fine so long as you trust all of the users on your system. Otherwise they could potentially get something running on port 22. Which, so long as you aren't actually sending auth info to 22, probably isn't a big deal.
As interesting and fun as honeypots are - unless it's your own gig, or the data from the honeypot fits into a larger security plan, it's just adding one more thing to manage. Move the port, run denyhosts, and in general just have access firewalled off to begin with.
Another way to look at it: If all companies only hire the top 1% of software developers (as a lot say), and in total employ 100,000 developers, this would have to result in 10,000,000 unemployed developers. Sounds a little unrealistic, doesn't it?
