1,471 karma · joined January 15, 2012
[ my public key: https://keybase.io/rohansingh; my proof: https://keybase.io/rohansingh/sigs/FYqfP0wJErPun-vsVRQ2fAEqahFzGh-6AGFTFN5MRYE ]
I'm almost OK with doing that, but I think it's a tall order my partner (non-technical) who has been using an Essential.
How would that even work? If I browse to any random public page of your website, it's served to me before you've even transmitted the terms of service. How could I be bound by those terms of service when I haven't even seen them?
You can follow this issue for updates: https://github.com/bazelbuild/rules_go/issues/512
That seems to live up with what was said further up the thread:
> People will put up with a lot of garbage if your product fills a need. And non-native UI is not even inherently garbage, just sub-optimal (and even that depends on the product)
That jives well with our product, but we do also need a mobile app to interface with the product. Flutter has been great in this regard. Dart and the declarative UX framework are very grokkable for backend folks.
The UI/UX is definitely good enough. Our app feels native, is snappy enough to get the job done, and looks way better than the native Android app we were trying to build before. Even if we were to have to go fully native down the road, Flutter is just the right tool for the job of getting us off the ground.
For a small team, there's just no way we could build both an iOS and Android app separately, on top of hardware, firmware, and a backend. It would kill us before we ever even launched.
I didn't realize how true this was until just last week. My partner was having a conversation with her friends (non-techies) about phones. One person mentioned that they are skeptical about whether Android is secure because it is open source. And that's why they stuck with their iPhone.
I left that startup soon after, but I heard that the backends for the GIS product really didn't have to be upgraded or revamped for years— PostGIS and GeoServer were just running solidly. Really a testament to the developers of those tools.
I'm actually a fan of the HERE Transit API. They've done the work of interfacing with a bunch of providers, and you can query their whole dataset with a REST API. Unfortunately it's proprietary and only free at small volumes. But I found it much easier to hook up than working directly with a transit agency.
That said, their coverage can be a bit random. For example, I ended up having to do direct GTFS-RT anyway because HERE doesn't seem to have real-time data for NYC subways.
Let's say you have some sort of model where a monthly subscription gives you an MIT license for all commits made that month. Who is actually going to go to the trouble of mirroring every commit or release from upstream to their own public repository? If somebody actually did that gratuitously, the copyright owner could just decline to renew their subscription the following month.
I'm sure there's some issues with this that I'm not thinking of, but I think generally if somebody is willing to pay you for a license, they're not going to be a jerk and try to undermine your business.
It completely weeds out robocalls, and no actual humans seem to have an issue with it. On the contrary, everyone sees why it's necessary.
Because eventually, something is going to die while a request is in-flight. So your batch processing needs to be able to recover from the "somebody tripped on the power cord" scenario.
There seem to be some other intermittent network issues as well. I just moved some stuff for a client off EKS and back onto ECS because it wasn't worth troubleshooting.
That said, I am not a fan of ECS at all. The scheduler is slow and it does really just take way too long for it to even start acting on new deployments.
Story time:
So, back in 2009, I'd just started working at Starbucks and my first job was to figure out some reporting discrepancies in online purchases of Starbucks cards. Basically, a report from the database on how many $$ of cards we'd sold didn't seem to match up with a transaction volume report from our credit card processor. And, as the new guy, I got stuck digging through stacks of classic ASP, layers of SQL Server stored procedures, and even some really old mainframe that I can't remember the model of. It was important to the business to figure out why these reports didn't match up, but it wasn't exactly a fun assignment that engineers were leaping onto.
Anyway, I eventually figured out that it wasn't a reporting error— we were truly "selling" more $$ in Starbucks cards than we were charging for. I dug through the whole process to see how this was possible, and found what it is still one of the most hilarious bugs I've found in my career.
When you got to the checkout form to buy a Starbucks card in any denomination, you had to fill out your credit card information. If anything you filled out didn't validate or we couldn't authorize your card, you would get an error message. It would ask you to correct the credit card information and resubmit the form. But, crucially, you didn't actually have to correct the information. You could just resubmit the form with anything you wanted, and some spaghetti logic determined that since validation & credit card auth had already been run once, it didn't have to be run again! Instead, we just created an order to ship you the product and didn't bother charging your card at all.
This bug was "leaking" probably over $100K in cards each year, for who knows how long. I still wonder if anyone actually figured it out and was exploiting it. It wasn't even "laundering" money, it was wholesale minting it.
The best part was a few weeks later, long after we'd fixed the bug. Someone from the IT security team showed up at my manager's desk with a lot of questions and pretty ready to walk "the new guy" out, and possibly press charges.
Turns out, while I was troubleshooting the bug, I'd accidentally submitted some absurd order. Something like 100 Starbucks cards, each loaded with $200 or whatever the maximum was. I guess I'd submitted it in production instead of the QA environment, and because of this bug, the order had actually gone through without charging me. It was a large enough order that it triggered a manual audit, and someone was pretty sure that I was just stealing from the company.
Talking them down was fun times, since they were pretty serious about the whole thing while my whole team was just cracking up :)
I worked on the team around 2009, before the rewards program rolled out. The card program was already huge at that point, so the rewards are not the primary draw.
It allows the attacker to potentially unmask your identity if you are logged into Zoom. When you join the call, you will show up in the participants list.
This is definitely something that you would not want to happen on various parts of the web. It kills your ability to browse privately.
As the article points out, diamonds naturally form in a high-pressure environment but are stable at standard atmosphere and temperature.
Am I doing the math wrong, or would that be less than two pints of beer at 5% ABV? Or does this not work with beer?
It's nice that jk are adjacent on Dvorak, and hl are conveniently placed as well.
They're probably trying to prepare it like a veggie burger, which ruins it.
I've had the Impossible Burger a few times, and just like ground beef, you can make a good burger or a bad burger.
The places that it turned out well, they were aware that it was meant to be prepared like meat. I order it medium-rare, like I do with beef, and it comes out well.
Another place that I've been to still thinks it's a veggie patty. They end up cooking it until it's dry and disappointing.
It gets to the point where some landlords do truly despicable things to drive out tenants who they cannot otherwise legally ask to leave. It also leads to things like tenants refusing necessary repairs because they fear the landlord will use that as a pretense to raise the rent or evict.
Basically, trust just breaks down on both sides.
Really not true. There is no part of the hiring process at FB that focuses on trying to find PHP (or now — Hack) developers. The main impetus was that there was an existing, large, PHP code base.
Disclaimer: former FB engineer
In theory this is all true, but you really have to look at the facts on the ground and the specific situation. Tons of folks have agreed with what you're saying, and poured in investment, and the situation remains really challenging. It's not for a lack of effort — India has a huge potential labor force, it's well-situated for shipping to emerging markets (like China, parts of Africa, or India itself). And, as was pointed out above, it has a strong democratic tradition that makes it appealing to Western investment.
But that same democratic tradition makes it a very different situation from China. It can take literal decades to organize and satisfy all the constituencies involved for projects like a power station, factory complex, or highway construction. Labor constituencies are strong and organized enough to seriously push back against projects, and are often skeptical of foreign investment and "interference". Political parties even resort to violence to stop initiatives that they disagree with.
I'm not saying that it's going to be like this forever. As a US national of Indian origin, I would be happy if the the situation was different so that I could work with manufacturing partners in India. Having some cultural and legal ties to the country would give me an advantage that I don't have when working with partners in Shenzhen or Shanghai.
But it's really just not the case right now. By all means, I'm happy that this investment is happening, but I think we need to be realistic. For a manufacturing ecosystem to develop that looks anything like China does, it's going to be more on the scale of 50 years or more, not 5-10.
The roads are narrow and dangerous, which also means that they are unreliable and slow. For example, it can routinely take 3-4 hours to travel just 60 miles, in a passenger vehicle. The issues only get worse if you need to move a large amount of materials or goods.
Many commercial and residential complexes in India do have a backup power source, but I don't think it would be feasible to run a factory off that.
Even though India now has a net surplus of electric generation, there are systemic problems with the electric grid. Some of them are due to poor infrastructure, others due to theft or corruption. But the takeaway is that a factory in India just can't run for 24 hours a day the way it can in China.
This is not likely to change in the foreseeable future, even with sustained international investment. There are a ton of constituencies in India that make fixing these kinds of issues much more complicated than in China. So while a company like Foxconn may be able to setup a factory and use their considerable resources to make it work, I don't think we're likely to see the kind of ecosystem pop up that you see in Shenzhen.