442 karma · joined February 15, 2011
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.
Health care is massively broken everywhere. I don't know how we move the incentives in the system to quality over quantity.
Does anyone have a strong reason they think that higher speeds and (I assume) low latencies would unlock something in the economy we're currently unable to achieve? I just don't see it.
[1] https://www.bloomberg.com/news/audio/2020-03-13/cristiano-am...
- 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 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.
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.
GPDR specifically allows for anonymized/aggregated data on app usage or marketing feedback: https://gdpr.eu/eu-gdpr-personal-data/
Is that "spyware"? Some would call it merely wanting to know if your marketing budget was wisely spent - I suppose a lot depends on what data it collects on people.
More info: https://developers.facebook.com/docs/app-ads
I suspect that a number of organizations that post free content and justify some/all of that expense with the marketing data they collect are going to look at changing that practice. More paywalls that require free user registration are the obvious next step. I wonder if that's not a step backwards for the Web.
If you're thinking long term and beyond the time period that you yourself will be employed at your org, you should put serious thought into making as vanilla and out-of-the-box a build as possible. My organization has a simple path to getting new developers up to speed on how to maintain and further update our Elastic Beanstalk-served sites: Learn the basics of how EB works and you're good to go.
On the other hand, if I had put together a superbly optimized AMI and grafted each site onto it, a whole lot of question marks start to appear. What distro is being run? Who/what's keeping it up to date? How do you connect to it? (On EB, you type "eb ssh" and it logs you in.) What's the load balancer setup look like? Where is all of this documented?
I think the trade-off of a few percentage points of optimization versus the fully-documented nature of a packaged service and the simplicity of getting someone new up to speed... I'll drop the few percentage points any day.
In fact, a few weeks ago a media org I frequent often had a site outage - they run WordPress so I offered to help (it was the weekend and I figured their IT guy might not be available) and they took me up on it. It took me five minutes to solve the issue and twenty-five minutes to understand how their custom, minimally documented setup was designed. I don't think that should be the norm.
Honestly - it's a pretty painless, AWS-takes-it-from-there setup.
I run our organization's WordPress sites on Elastic Beanstalk (just do a "eb deploy" from your Git repo of the site and it gets up there), plus RDS (Amazon Aurora) and CloudFront. EB and Aurora auto-scale and CloudFront does its CDN thing.
I highly, highly recommend Elastic Beanstalk ( https://aws.amazon.com/elasticbeanstalk/ ) to anyone who wants their org to concentrate on creating value (new/better code) and being cost-efficient (use the compute power needed that minute instead of overprovisioning) instead of fiddling with custom server configs and wondering if you're fully patched up. It was a game changer for us.
https://geocities.restorativland.org/TimesSquare/Arcade/2516...
People do of course share those articles, but they don't seem to look for or trust web page share buttons. Even I rather copy/paste the URL into Facebook myself while on a desktop/laptop, or use my browser's built-in sharing functionality on a mobile device. This is all anecdotal but also based on data from hundreds of millions of page views.
But to me, one of the most significant advantages PHP has is that its documentation is terrific. PHP.net is simple, clear about parameters and return values (as clear as PHP lets it be anyways) and best of all has a terrific comments / examples section for each function.
Better documented is better.