HN user

busted

379 karma
Posts5
Comments76
View on HN

I've thought about this in the past. There's a modern way to build architecture, and cloud providers are in general only providing the building blocks and requiring you to put them together. It's unscalable to expect every company to hire someone smart enough to construct a good architecture (let alone the time) but at the same time, people who have been working on infrastructure long enough know that there's really only a handful of useful architectures that solve 90% of problems. I thought of it as CTO-as-a-service or CTO-in-a-box.

Service meshes like istio.io start to solve a portion of this.

Almost certainly there is endless complexity but I bet you can come up with something useful. Good luck!

I hadn't seen this before, really cool. Found more information on Wikipedia:

In 1991, the United States Congress passed the ISTEA Transportation Authorization bill, which instructed USDOT to "demonstrate an automated vehicle and highway system by 1997." The Federal Highway Administration took on this task, first with a series of Precursor Systems Analyses and then by establishing the National Automated Highway System Consortium (NAHSC). This cost-shared project was led by FHWA and General Motors, with Caltrans, Delco, Parsons Brinkerhoff, Bechtel, UC-Berkeley, Carnegie Mellon University, and Lockheed Martin as additional partners. Extensive systems engineering work and research culminated in Demo '97 on I-15 in San Diego, California, in which about 20 automated vehicles, including cars, buses, and trucks, were demonstrated to thousands of onlookers, attracting extensive media coverage. The demonstrations involved close-headway platooning intended to operate in segregated traffic, as well as "free agent" vehicles intended to operate in mixed traffic. Other carmakers were invited to demonstrate their systems, such that Toyota and Honda also participated. While the subsequent aim was to produce a system design to aid commercialization, the program was cancelled in the late 1990s due to tightening research budgets at USDOT. Overall funding for the program was in the range of $90 million. (https://en.wikipedia.org/wiki/History_of_self-driving_cars)

7 years later there was the first DARPA Grand Challenge, where no cars completed successfully. There's a great episode of startup podcast with interviews of the original competitors: https://www.gimletmedia.com/startup/grand-challenge-season-6....

It's interesting to wonder whether and how much farther we'd be with self driving cars and computer vision in general if the government had continued to put its resources behind this project.

Certainly agree with most of this. It has a couple of underlying ideas that I've also noticed.

1. Use empathy to both overcome resistance and do the right thing. The strategy in Step 2 for reframing an interaction in a way that gets the person to understand that you're trying to help them, and also reminds you to remove your ego and that the goal is to improve things for everyone, is one I've used a lot. Not because people think you're trying to be difficult but because it overcomes defensive barriers and helps ease them into the context switch of thinking about the problem.

2. Get a foothold with iterative progress. The author did this by splitting adoption and (the process for) configuration. Especially with tools and processes, people will often try to jump to the final state and if they can find any holes or issues with the proposal as is they'll be inclined to throw it all out at the start. If you instead make it clear that we're a) trying something new that will b) be improved as we learn more about it and c) can always be reversed if we decide it was a bad idea, people are usually much more open to it.

One thing the article mentions though is "spending" leadership capital. I like instead to think of it as "investing" capital. If the decision you invested it in ends up being bad, you lose it. If it ends up making people's lives better, you've gained more. Thinking about it this way also can get junior people, as mentioned in the article, to be more inclined to help with decision making. They don't have a lot of capital to spend but they can choose to invest the little capital they have in order to grow it.

The amount of Elon Musk hate I see online is crazy. It seems like people are hellbent on hating this guy. When he announced that Tesla could help Puerto Rico, the number of snarky and demeaning comments was huge. Now, so quickly, they've actually accomplished something good. I wonder if any of those snarky people, most of which probably did nothing to help Puerto Rico, will care.

This article is kind of absurd in its assumption, I think it's irresponsible. By saying that you thought police would modify their behavior in response to being filmed, and especially (but not only) by citing a bunch of studies where CRIMINALS changed their behavior in response to being filmed, you are implying that the officers would change their behavior because THEY KNOW THEIR BEHAVIOR IS WRONG and they were doing it anyway. You're essentially saying you are surprised more officers are not actively criminals.

The actual problem is more likely that in the vast majority of incidents officers DO NOT KNOW what they're doing is wrong, that for instance they're acting with bias or unreasonably against someone of color in a way they wouldn't act against a white person. The ACTUAL purpose of the body cameras is to create a record that allows ACCOUNTABILITY for officers ("I felt threatened" with no evidence is no longer enough to justify a shooting). Only with that accountability can we start to PROVE that officers are acting unfairly whether they consciously intend to or not, and then fix the problem (with "training" as the article says but with no detail may as well have been saying nothing).

working a job they probably don't necessarily like very much

Worse yet, trying to make tech people feel bad just for finding a job they actually like and going to a city where those jobs exist! If only we could all be so lucky. Like the job or not, I haven't seen very much indication that people are going into tech in droves just for the money (unlike what I assume you see in banking).

I was able to use one of these at Google Next. It's pretty reasonable but I was still unimpressed. I have a very simple test for drawing applications that represents something I would do in reality: draw a system diagram with multiple components by drawing and labeling a couple components, copying them multiple times, drawing arrows between them as appropriate, and then rearranging it in a new way.

I very quickly found early limitations of the jamboard like (iirc) not being able to copy drawings or group text and drawings. I'm sure over time the programming will get better.

Update: CRISPR 9 years ago

Crazy. There is basically an international consensus that editing viable human embryos is unethical and China just doesn't give a damn.

There is a comment on this article basically saying, "I bought a Vizio TV, later my email, bank account, and facebook got hacked, and now I know why." Shows roughly the understanding of these issues for some people.

It's interesting to me that you probably don't care that this isn't true, nor is it true that Twitter ever decides to not show your tweets to a subset of your followers through a "shadowban". You just say whatever. Doesn't affect you whether it's true or not and if other people believe you, hey that's pretty funny that people just believe things you make up or misunderstood.

It's kind of amazing that very few of what you would naively expect to be the "best" domain names, especially for selling things, are actually home to successful business. Things like shoes.com, pizza.com, clothes.com, beer.com, programming.com, they're all failed or nothing. Others (books.com, computers.com) just redirect to websites that are closely or tangentially related.

I've worked in a 2-person office, in a cubicle, and in open office plans of various sizes. I personally prefer the open office format. It makes the team feel more cohesive, it makes me able to jump in to problems that are happening, and it's never stopped me from doing work that requires deep concentration. And if I really wanted to, I could book a small conference room or go to a corner booth somewhere away from my team and work there, but I don't ever feel the need to.

If you create a frontend, it may be a good idea to add a button for buying a print (which you could do through one of the many online services available). Some of these look very nice and I'm considering printing something like this on a canvas to hang on the wall.

Isn't it at all possible that it's some kind of mistake? Miscommunication, different prices changing at different times, and/or people not caring led to them being priced the same? It's not as if the two options are the same price at every single McDonalds, just this one.

Not OK, Google 11 years ago

Hotword Search Enabled No

Always-on Hotword Search Enabled No

It's already disabled.

I don't understand the outrage here. I remember chrome asking me if I want it listening all the time for "Ok Google", I thought "Obviously not" and said no, and that was the end of it.

I'll wait until the site is responding faster/not erroring to be sure but if it's really as it appears, this is amazing. Attractive customizable design is one thing, but real logins, real graph relationships, real feeds, real filtering for mentions, user photo uploads, potentially real messaging, all without any coding would be (is?) really amazing and covers 99% of all the site creations any laymen could want.

It doesn't need to scale especially well for the vast majority of customers. If your first reaction is "this doesn't scale" or "this doesn't eliminate programmers" you have to be a professional point-misser. I'd want to see how intuitive the interface for making this is but it's cool stuff, and as it matures I'm sure will only get more interesting.