yllus

Mike, Raymond - big fan and daily user of the webcam. Congratulations on the new product launch announcement, very interested in becoming a customer!

Congratulations to the founders for the launch, but unfortunately I had the same response.

In situations like these - intrigued but with no real understanding of what the product is - I want the video to show me a real-world example in about ten seconds flat. A more glitzy promo video has its place, but not in a post to Hacker News.

This is phenomenal work. A genuinely modern take on MUDs of old. Is multiplayer already implemented? I'm weirdly interested in starting up a good old MUD clan/guild again on an all-player killer server...

It's anecdotal, but unfortunately I'd say that the experience is much the same in single-payer Canada. I have never had a GP who is not trying to rush me out of their office as they seem to get paid by the amount of patients they see, not the quality and depth of care they provide. I now declare I have X questions up front and then work my way through them, ignoring the GP's repeated attempts to bring the appointment to a close before I'm ready.

Health care is massively broken everywhere. I don't know how we move the incentives in the system to quality over quantity.

Nice deck! And terrific market positioning; in doing my own research of trying to get all organizational data in a single place in an otherwise non-technical organization, I've done demos of Fivetran and a few of your other competitors and your analysis of their weaknesses are spot on. I'll be giving your product a try.

Really interesting concept and product - perfect for the times we're in! Desperately needs a video of the product in action on that home page, get on it! :)

I'm all for an Assassin's Creed style augmented reality view of the world! But I don't see why it's something 5G would usher in over 4G (or 3G).

It's an incredibly busy position if you're doing it right! I've had development teams of 4 - 20 reporting to me, and I think my responsibilities have generally included:

- Being the point of contact between Development and the rest of the organization, fielding questions about what can and can't be done, plus t-shirt sizing on effort

- Keeping tooling and technology unified (not ending up with one project each using Vue.js, React, Ember, Angular...)

- Keeping up standards (around code reviews, documentation, testing and alerts, end user and developer training)

- Thinking long term about how features, services and tools being built today can be re-used tomorrow

- Decisions about budgets and how to approach a project (use internal people or outsource to a vendor; field RFP responses; negotiate and get paperwork signed)

A lot of communication (inter-team and intra-team), budget work and "architecting" stuff is a reasonable summary, I think.

I'm curious about a related question: Does a manager need to be the best coder on the team? How much does it help/hurt if they're not?

It still comes down to: Would you rather be seen as someone who creates value (profit), which is a "developer", or who works on odds and ends for the company and ultimately costs money, a "programmer"? Given the two options I think the most advantageous option is obvious.

I will admit however that my view on this is rather arbitrary. I don't think we really have a good way to resolve what's best.

Let's not make Mr. Esper out to be doing this for any other reason than because of the strong and immediate backlash from the violent street-clearing that occurred in DC. This is the same guy who said to state governors, "I think the sooner that you mass and dominate the battlespace, the quicker this dissipates and we can get back to the right normal." He is no champion of individual rights.

To draw anecdotally from my own experiences, its for two reasons:

1. It's simple to get started with, but complex enough to tweak to your needs in respect to simplicity of deployment, scaling and resource definition.

2. It's appealingly cloud-agnostic just at the time where multiple cloud providers are all becoming viable and competitive.

I think it's more #2 and #1; as always, timing is everything.

Sorry, use of the term GUID confused things - I meant that if an identifier string is generated when you click on the ad, and the purpose is to simply see if that identifier completes the app install and first use - that's not against GPDR. (In my head GUID means "unique identifier string".) Storing the GUID tells you nothing other than some device clicked on an ad and some device did or did not complete the app install.