yeah something like that is decently easy on web... I think it may be a more significant challenge on the Mobile side. I'm also curious about things like... should we have 1 github repository for the base app and then branches for each customer, or some other type of code management setup.
I haven't done this for mobile but have done for web. I imagine for mobile it becomes part of yout build process? Eg. Your build runs and looks for a config named like the client name, from there you swap out designs.
For Github we had the base app in one repo and client apps in their own repos. This was more out of necessity as we had different clients on different versions of the product / with their own custom functionality.
That's not a good use of branches. A live product shouldn't need to pull in 100 branches.... Just keep it simple, a directory called branding with a subdirectory for each client. Ideally shouldn't be code, just assets and maybe a simple css or color file.
I've hired many people in Peru for projects over the past few years. Your strategy is a good one. Having a solid Github portfolio and/or references from other people you've worked with is very important.
Heavily trafficked sites are already paying for a "fast lane" in the form of CDNs that cache everything but dynamic content. These CDNs already have interconnect agreements with the large ISPs (and have for years).
Interconnect agreements are different than "fast/slow lane". CDNs will need to pay a premium so that their traffic will not be slowed down, regardless of the peering agreement.
Interconnects are exactly what the "fast/slow lane" argument is about. Netflix bought interconnects from Comcast and Verizon. Just through buying interconnects to the ISPs, the CDNs ensure their traffic won't be slowed down by an intermediary like Cogent.
They're not intending to provide higher QoS for sites that pay up -- that's insane and it wouldn't work anyway.
It's my understanding that interconnect agreements solve congestion on the network by having a larger connection to infrastructure.
Fast/slow lane practices throttle that connection, regardless of how large the pipe is.
So, my small business website could be using a large internet connection that technically has plenty of bandwidth to carry my traffic but, unless I pay Comcast a premium, traffic from my website will be put in the slow lane and throttled back.
Then your understanding is incorrect (sorry; not trying to be flippant). Interconnects are the entire story here.
The media has framed a lot of the congestion issues in the context of "fast/slow lane" but what they come down to are business disagreements between the transit providers and the ISPs. The solution to these disagreements from the viewpoint of a large service provider is to purchase an interconnect directly to the ISPs. If you are a small service provider, the solution is to purchase delivery through a CDN. Netflix used to purchase delivery through CDNs until it got too expensive for their business model; so they started building their own CDN that they called "OpenConnect". They used their positive brand image in conjunction with the ISP's poor brand image to launch a PR campaign with the goal of knocking down the price they would have to pay for interconnect service. It worked; they knew they were always going to have to pay the Comcasts and Verizons of the world but they were able to talk the ISPs down a significant amount.
Strategically, it's a bad position to be in for a service provider because the ISPs can raise the price at any time (which is why Netflix has continued complaining about it). But realistically, the ISPs sit on such a strong market control point that nothing can really stop them from setting prices (common carrier status just means they have to offer the same price structure to everyone; not that they can't arbitrarily raise prices).
No, you wouldn't. The thing is that all that top wealth is managed by a group of accountants and lawyers. Highly professional accountants and lawyers. (My friend is an accountant here in Silicon Valley who manages wealth for billionaires in a large accounting firm. He describes me some ways how they manage wealth.) So these people's role role, their only role, is wealth preservation, meaning tax minimization and avoidance. They know all the laws, rules and regulations, and they have fiduciary duty to manage the wealth efficiently and conservatively. Hence they will go to tax heavens and offshore, if needed.
If you're not in the highest marginal rate bracket, or most of your income is not investment income, it's generally not worth the expense of paying for these services.
Fees for these services generally start at $10,000, and only go up from there.
Yes, but the process of creating and more importantly updating that software would involve so much human input that you wouldn't end up with much of a net gain in terms of time or costs saved.
US federal tax laws change every year, and are so interconnected that quite frequently small changes in one tax law can have massive impacts on entirely different areas of law. And that doesn't even take into account state and local taxes, or the taxes of the foreign jurisdictions you'd be dealing with, or the impacts that tax treaties could have, or even the impact that non-tax laws may have on financial transactions.
I can tell you the majority of angel investors in Dallas I've talked to that do not have experience with west coast deals do not like convertible notes.
We closed a note with Dallas investors that DID have experience w/ west coast deals that featured a cap and a discount.
