Unless the user taps the ad, no JS or HTML is involved, which eliminates the possibility of such tricks.
I looked for such a library a while back, but didn't find any.
1,169 karma · joined August 15, 2014
Unless the user taps the ad, no JS or HTML is involved, which eliminates the possibility of such tricks.
I looked for such a library a while back, but didn't find any.
Of course, the quality won't be as good as something done by a professional, but the question is that since we don't have a HD DS9, whether the version produced by an automated system is noticeably better than what we have.
About basic, yes, that's a pain.
Do you want to optimise pause times? Use X. Optimise throughput without regard to pause times? Use Y. Optimise memory use? Use Z.
It may not be accurate in every case (no guideline is), but it would be a good starting point for the vast majority of us who don't know the pros and cons of various collectors.
Actually, separating out the things should be modified from things that shouldn't would be a significant improvement. Like:
# Section 1: Configuration: Change this as appropriate:
FOO =
BAR =
# Section 2: Logic: Don't change this:
...
According to my CA, individuals might be eligible for both depending on what they do. It's not just for businesses. If you're providing a service, like a freelance programmer, it's 50%. But if you're building your own product, it's 8%. Or some such distinction.
In any case, the script supports both; just change the parameter.
This script determines:
- When you're made an offer for a given CTC, how much will you take home every month?
- If you want a certain amount of take-home pay every month, what CTC should you ask for? This is for Indians.
This script handles:
- Differing tax treatments for employees and consultants. The latter are eligible for presumptive taxation under section 44AD.
- Health and education cess
- Surcharge
- GST
- PF and pension
- Section 80C investments
- Professional tax
Likewise, all of AR doesn't need the kind of information only a few companies have. Think of assembling something at home, like furniture. Or a car mechanic. Or astronaut. Or soldiers. Different companies may control relevant data sets in different domains, and some may not even be data-intensive like furniture assembly.
First, I'd look at setting up automation and boundaries. If I'm launching a new service and it's insecure, hackers shouldn't have free reign in the datacenter, say to send RPCs to any other service they want. It should be like a public cloud. Or if a config file was edited in a way that's malformed, the solution might be to have automated tests that run as part of presubmit. There should also be clear documentation of dos and don'ts that you wouldn't have to understand all the implementation details to use effectively.
Beyond that, some checks will always be required. My post was intended as more of a "if possible, do this instead of that" than in a binary sense.
Splitting probably makes sense only for an infrequently used feature, like video chat in an app like Gmail or Slack.
The managers I respected were all TLs who were the most important engineer on the project.
Going back to your point, the TL would be the best person to evaluate the engineers who work under them. 1:1s, growth discussions, etc should all be conducted with someone who knows your work intimately, which means the TL. Which means the TL is a manager.
There's still room for EMs to be more technical or more people/coordination-oriented. A technical EM would take responsibility for a smaller area (backend) and go deep technically into it, having the most impact as an individual contributor, knowing all the code, being able to debug any part of the system, being the go to person for everything in that area. Everyone in the backend would report to him.
An EM can also decide to be focused more on people/coordination. They'd take responsibility for a bigger area (backend, frontend, iOS and Android) and go wide rather than deep. If you ask them how to debug an iOS app that crashes in the background, they may not be the best person for that.
But in both cases, they're managers, not TLs.
Having said that, maybe you're responding to one part of the article, and I'm responding to another, so we're talking past each other.
Regarding your point that this tax will be hard to enforce, why do you think this is harder than to enforce than the cornucopia of taxes and construction rules we have today?
Regarding your point about leaving buildings 80% finished, there can be another tax on land not put to productive use. This would include both land left empty, and unfinished construction. In return for these taxes, eliminate other taxes like property tax, stamp duty, registration, transfer of ownership, etc.
With this, millions of people who're homeless will suddenly find a home. Investments that have already been made will be useful to society, which should be the case to begin with.
If this policy deters investment in housing, rents will eventually rise till it again becomes sensible to invest in building houses. The market takes care of itself.
Instead of a ban, perhaps a high annual tax, say 30% of the value of the house, if it's left empty for more than a month a year.
Mac only.
It does, when coupled with variable pay they could lose if their project doesn't work out.
> There are plenty of lazy people who don't care who are not paid maximum possible.
And those lazy people will then find jobs at other big companies, where they don't have to work hard and still make more, more appealing.
Your salary is below market rate, but not when you include variable pay, in startups, and in my proposal.