HN user
Head of IT at Xamarin. Productively lazy; automates everything within reach.
I actually think that the tax treatment differs as well - the 2 months free can be treated as a marketing expense, whereas the reduced rent simply results in the lower revenue.
For financed buildings it also keeps the nominal value of the building at the same level - it's still technically "rented" for the same rate, keeping future cash flow projected the same.
Yeah, the “enterprise” product lineage is more Live Communicator -> Office Communicator -> Lync -> Skype for Business (kinda direct link to, even though it’s SaaS only) -> Teams
Well, they may export crude, but without refinery capacity they are probably capped at the rate they can produce usable product.
How is that an enormous dose? The recommendation is 2x200mg every 4-6h. When doing competitive athletics, I probably took 1-3g of “vitamin I” a day.
600mg a day is barely above a single dose.
I think I'd be willing to pay more to offset higher content costs for more theater/blockbuster type movies. If Netflix was say 14.99 instead, I wonder what that would do to help? Perhaps splitting the content between tiers? It would shrink their "user base" for the purposes of streaming, allowing higher per-user payments on a title-by-title basis.
Sad part is, I know they are trying to lower that amount, and show that content providers need them as much/more than Netflix needs their content, but as a consumer, I'd like the options.
System Engineer - Boston - Fulltime
Systems Engineering Intern - San Francisco - INTERN
Xamarin IT is looking for an FTE systems engineer in Boston, and an intern in SF to come in and help build out our internal infrastructure. These are both hands on roles helping to build our internal infrastructure, improve monitoring tooling, and help drive automation and standardization.
if you're interested please email me at Nick.IT at xamarin dot com
That works until you get into anything complicated. Recently, I had a spreadsheet that our finance team built that provided different calculated values (for a multi table aggregation, nothing simple for sure) on Excel Windows and Excel OS X. This is not an uncommon problem - I've seen it a handful of times. Excel for OS X is at about 90+% parity with Excel for Windows.
This only bites you occasionally, but when you are a spreadsheet driven org (e.g. Finance groups in a company) you often need the performance/top-end feature set of Excel for Windows.
Sure it can - think of smallpox: the first smallpox "vaccine" was actually inoculation with cowpox - a similar, but less virulent virus. The provoked immune response rendered a smallpox infection less lethal, and provided a measure of protection.
Realistically, these are all the same thing in different manners - dissolving a business, and starting another immediately competing in the same space, which seems shockingly sensible to me.
Yeah, I remembered that wasn't the right pairing after I wrote that (and thankfully ours weren't paired like that, we had the right names); but that also goes to show you the downside of that particular naming scheme - it requires additional knowledge in a specific domain.
I used to run a dual stack app, windows was Roman mythology, linux was Greek, that allowed us to keep roles straight across environments - apollo/hermes, athena/minerva, etc.
This is technically true for MOST taxes in the USA. Generally municipalities have reciprocal agreements with each other, but when tax is fixed at a state or municipality level, you generally are supposed to file proof of tax payment in the location of purchase, and that is then generally applied as a credit against any tax burden imposed on the place of use. A perfect example is income tax in the US if you work in one state, but reside in another.
It's inefficient, but how else would a local tax scheme be at all enforceable?
You can be allergic to certain common components, e.g. egg albumin.
Addressing number 1, I saw the other day a study that indicates that this can back fire for individuals with low self-esteem. [1]
I think it's a fine line- I'm not in finance, but from what I understand you want some incentive to purchase a new issue as you have a set target of shares you're trying to move. I think that doubling in price is a bad thing, but I don't think movement of a few dollars per share is necessarily a bad thing.
There's no requirement to go "public" in the sense of listing on an exchange, and available for public purchase. What changes at that point is SEC regulatory compliance kicks in: earnings/revenue go public, SEC compliance paperwork has to be filed just like a public corp. That's really why people try to stay under that number - you have all the drawbacks of being public, except a floated share price, and it would effective crush any IPO pop that they would expect to get, as financials would be totally available, so offer price would have to reflect the company's financials.
The issue with credit card vs cash is actually far more nuanced. For example, in Boston, cab drivers don't get to choose a payment processor, the processor/cab company takes about a 8-12% cut of the total, and it's quite often subject to payment delays of 3-5 days between fare and receipt of funds. Compared to cash, that's a pretty raw deal, and for someone who's shelling out a bunch of money to rent the cab, and run it, can be sometimes the difference between profiting on a fare and not.
I think the issue is more that the ISPs are demanding payment at both ends of the tunnel. They charge you and I for transit (best-effort though it may be) and then when a bulk of their customers traffic turns to a popular network, attempt to charge that network to upgrade their port speed. (something which is customarily handled for free between peered carriers since both are charging their customers) Think of it this way - it's as if I pay UPS to send packages and then they request fees from the cities they deliver to, or they only deliver 100 packages a day to the municipality. That would be insane, and laughed out of court, but that's what Comcast/Verizon are doing.
Also, intentionally physically underprovisioning the connection is throttling, plain and simple. You are limiting the amount of traffic that can traverse that network boundary to 10G/40G/Whatever your port speed is. What difference does it make if I do it in software or simply refuse to bind more ports to the team?
Thank you for the gogetssl.com link. I've been looking for a multi-SAN/wildcard cert that wasn't insanely expensive.
From the DOL: "Being paid on a “salary basis” means an employee regularly receives a predetermined amount of compensation each pay period on a weekly, or less frequent, basis. The predetermined amount cannot be reduced because of variations in the quality or quantity of the employee’s work. Subject to exceptions listed below, an exempt employee must receive the full salary for any week in which the employee performs any work. "
Salaried employment isn't contingent on any hour requirement whatsoever. I could work 1 hour a week and still legally qualify for my salary. My employer could give me enough work to require that I stay in the office for 80-100h, and I would have to do so to fulfill the job duties.
I in no way stated that exempt employees can't have other employment. I have always maintained a consulting practice while working - what I can't believe is that people don't get it in writing that they are doing this, and carve out the things that their employer doesn't get to touch. Exemption/Exclusion clauses work both ways. It avoids this situation altogether. For a computer professional who branches out into other semi related tasks, I would consider this essential. Plus, I think that there's a large difference between something completely out of your field (like the real estate and restaurant ventures mentioned) and another software/gaming company.
This is why you sign an exclusion clause when you start anywhere. I don't know why this is so crazy. Salaried employees are paid regardless of hours worked, which means that you are technically always employed, regardless if you're expected to be working.
If you're paid hourly, then there's a clear demarcation between working hours and not, being a salaried employee blurs that line. That's why many states have regulations as to who can be salaried and how.
Running headless virtualization on a server with KVM?
Sure, for a desktop system it might make sense, but headless systems might be better served with QEMU-KVM.
They also argue that this poses a long-term potential problem for VC as well. Eventually an institutional investor wants their money back. Eventually they have to settle up and see who the Amazons are vs. the Pets.com. That forces businesses to transition towards exit in some fashion, if they move to IPO, this shift forces them to make a shift (to become profitable) which will kill some.
I don't see how that's a controversial point, but it's a distinction that a lot of people who aren't in tech, or around startups don't get.
How does this work for internal applications?
I looked through your site, and couldn't find any documentation without creating an account.
I've served in an operations capacity for exclusively *-nix, mixed-stack and primarily MS environments, and I will say that from my perspective the OSS community has more news, but I find that there's less that I actually care about.
I've actually been finding MS products more easy to work with lately, while Ubuntu has been getting more frustrating. Some of that is due to familiarity, but there's also a lot of decisions I've not agreed with. In general, I like that I can write something that works for a few years in Windows - I don't have to worry if the latest package updates are going to break everything. I've lost weeks fixing dependency bugs, and I don't seem to have the same issues on Windows.
But at step 3, you've already validated the code change. You know that the name only code works as intended, and you're just cleaning up old code at that point. I do agree that there is a potential for failure at that point, but I'd think it to be reasonably mitigated in comparison to making the change and needing to then roll back.
Step 4 is non destructive from a data perspective, as those columns would be "zombie" data. they'd exist, but nothing would be referencing them at that point, and the data would simply exist in a different form.
If you're talking about representing the data differently, yes that would happen, and in a case like the above, you'd be much better off by preserving normalization and using a view to combine into a "name" entity. Th
That's why you apply the approach he was stating - you move slowly. Step 1. insert name column and populate from fn/ln. Step 2. Change code to point to name column as well as populate fn/ln Step 3. remove code pointing to fn/ln. Step 4. remove fn/ln columns.
No loss of data, instant reversion at any point, because each step is non-destructive. It's just longer, harder to do in reality, but definitely the "right" way to do it if you are 100% concerned with data validity.
I think the tough part would be making the transition onto mobile, and integrating the SMS/calling aspect into it. Yes, you've got the brand with MSN Messenger, but expanding that takes a vision of communications that I don't know MS had c.2009 when they would've needed to launch.
I can see both sides of the coin though - for a company that is as heavily cloud-invested as Netflix is - it might make less sense to maintain a cage for internal IT in a few datacenters. That said, I do get worried about sensitive data in the cloud.
I didn't get that he was talking about moving to cloud/SaaS vendors as a whole, but more the IaaS/PaaS space - the "Hey, this app runs RoR, can I just run it from a Heroku dyno rather than a VMWare box in a cage" type of move. Granted, there's still a cost associated with that, and a need to plan the move, but it's less of an issue. They are making heavy use of SAML SSO it appears, so the account/vendor thing probably wouldn't be as much of an issue.
This is what I think of whenever someone talks to me about certifications...