1,659 karma · joined July 18, 2019
Docker registries are how things are done right now. And the changes to Docker Hub that happened this week have a significant impact on the Docker ecosystem. This announcement is about solving that impact now, because developers need a solution now. This doesn't have anything to do with any hypothetical improvements to the Docker ecosystem or Docker data usage that may otherwise be in progress by [insert company here].
Do you work for a company that just gives away all of their services and products for free, or...?
>Also, "500GB/mo.", at launch. Let's not forget those generous free limits can be slashed whenever it suits, and why they might be so generous for launch at all.
AWS has, to my knowledge, never increased the cost of any service after launch. They do, however, have a long history of reducing prices.
You also completely neglected to mention this part:
>Simply authenticating with an AWS account increases free data bandwidth up to 5 TB each month when pulling images from the internet. And finally, workloads running in AWS will get unlimited data bandwidth from any region when pulling publicly shared images hosted on AWS.
So yes, AWS gives some incentive to create an AWS account, and an even further incentive to use AWS services. All I can say to that is... duh?
The water gets muddied because that partner may not actually be involved in the project very much, and in controversial situations they may try to blame someone else (such as a lower level firm employee who was involved) for any mistakes, but at the end of the day the partner who signed their name to the contract is the person held accountable.
Once you are promoted to partner, you are no longer an employee of the firm and in some cases you no longer earn a salary. Instead when you are promoted to partner, you are allowed to "buy in" by purchasing a certain number of shares of the company. Once you own those shares you are then part-owner of the firm (rather than an employee) and enjoy profit-sharing.
Yes and no. In practice, each "country firm" (such as the PwC US firm) operate as individual companies with their own leadership team that, while they don't have the typical CxO titles, they have the same roles. Tim Ryan is basically the CEO of PwC US, for example, and PwC UK is a different company with a different CEO.
Internationally there is also an umbrella organization that helps coordinate really high level stuff like branding (since all the country organizations share the same branding), internal IT strategy (such as getting everyone to use the same productivity tools to make it easier for cross-firm collaboration), etc.
The individual companies reap benefits from this coordination because of the singular, strengthened brand, culture, methodology etc. So in that way it sort of is like a franchise. But that international organization doesn't have much to do with the day-to-day in-country operations or decisions about specific audits/projects. That would be the responsibility of the local partners/leadership team.
I don't think I ever realized how much of this venting must have subtly happened in person, but since COVID I think most of it gets bottled up and people get very frustrated when they can't casually talk through these issues in person. My team has collectively agreed that these "venting calls" are great if only for the reason that they make you aware that you're not the only one with frustrations, and I think that really helps morale.
For me, being co-workers is just one small facet of our friendship. We do talk about work sometimes, just like sometimes we talk about sports teams we have in common or other hobbies. But we don't only talk about work. I don't feel that my perspective is limited at all because my co-workers have introduced me to their spouses, who might be in totally different industries, or to new hobbies such as surfing or soccer, or brought me along on trips to new places or encouraged me to volunteer. All of these things have expanded my perspective greatly, and if you trace them back far enough, all of them are originating from my co-workers.
In your startup example, I have been on teams where this culture was the case, and certainly with some people I have completely lost touch after they/I left the team. But for others, even though we worked together work was not the dominating reason that we were friends. When I left the team we lost that one facet of our relationship, but our friendship still survives because we have many other facets that facilitate it.
So I think the problem isn't when someone's social circle aligns strictly with work. I think that's fine. I think the problem you are describing is when it turns into a "work-dominant social circle" rather than "a social circle that just happens to have the same employer in common".
Furthermore, I think the "anti work friend" attitude is counterproductive to this. People are saying "don't spend your time building friendships with co-workers because if you leave work you will lose your friend". But if you carry this attitude and don't build a friendship that is strong outside of work, then of course your perspective is going to be limited to work, and of course you will lose your friendship with that person once your work ends. It's a self fulfilling prophecy.
My boss and I have a good enough relationship at work where I'm 1000% confident this wouldn't happen, and if said boss did "perceive" some kind of drop in productivity, their response would be to help me with that rather than turn it into a negative. Indeed, during COVID when I expressed to my boss that I was having a tough time, his immediate response was to ask how he could help and to offer me a couple days off to recharge.
And the reason we have that relationship is specifically because we treat each other as friends that also happen to have a working relationship, rather than letting the work relationship dominate all else.
Not everyone will have that kind of relationship with their boss, but I believe it is something everyone should aspire to rather than immediately rejecting it as even a possibility.
I would absolutely share this with my "work friends" and even my current boss. When one of my previous bosses shared with me that he was having trouble at home with his spouse, it wasn't like he suddenly became a bad boss. If anything, it helped our work because it gave me the opportunity to be more understanding when he seemed more worn out or needed to leave early for the day to go spend time with his family. If he had told me he was struggling with drinking, then I would know that maybe we should go play sports rather than to our weekly happy hour. We build each other up, both inside and outside of work, because that's what friends do, and it has the nice side effect of making our professional careers better, too.
Perhaps I just have had a lucky stream of working on unicorn teams, but I would hate to work at a company where I couldn't share details of my life with the people that I spend 40-60+ hours a week with. Obviously every workplace and relationship is unique and you aren't going to share everything with everybody (I'd share the above details with my current boss but by no means with all of my bosses), but I don't understand this attitude that you shouldn't share anything with anyone that happens to have a common employer.
To me, work is just another facet of our relationship alongside the many other facets, no different than if we had met through volunteering or went to the same gym. I don't share everything with every coworker, just like I don't share everything with every other person that visits my gym. But I also don't shy away from sharing things with someone just because they are my coworker, just like I wouldn't shy away from sharing things with someone just because they also use the same weight set that I do.
Outside of work, my "work friends" and I go out to eat, go play sports together, hang out at each other's houses, etc. We talk about work sometimes because it's obviously a common interest, but our friendship doesn't revolve around it, and if someone severs their relationship with the employer that we have in common, it does not mean our friendship also severs.
It really saddens me whenever I see this (apparently common) sentiment on HN. Through every job I've had, I've met some of my very best life-long friends. My wedding party is over half people that I met at work. A couple of my former bosses are people I see every couple of months (pre-covid) and are invited to my wedding. Even one of my past clients is someone that I keep in touch with regularly (for nothing related to work).
Not everyone at work is going to become your best friend, but if you're automatically assuming that anyone you meet through your job is completely "off limits" for friendship, you're really hurting yourself. I can't imagine working at a place like that.
Then, even after you fire them (or let's even say by some miracle you were able to fire them quickly), it costs a lot of money and time to hire someone new. That's yet more time and budget that isn't going into your team, and your team is also a person short while you go through the process of hiring and then training.
It is leagues and leagues better for "the slacker situation" to not be a problem at all, and it is much less likely to be a problem if prospective slackers aren't given the opportunity to slack off at home to begin with.
My experience is the complete opposite. I spent a lot of time at a very large company that has always had a "WFH if you want" policy. By and large, the highly productive people were doing a hybrid work-from-office 3-4 days a week and WFH 1-2 days a week. In contrast, the people who self-selected into always WFH were almost exclusively slackers who took advantage of the situation to watch Netflix or sit at the pool all day and get nothing done.
I know it's just an anecdote, but I think it's important because this is probably what executives are most worried about. It doesn't take very much effort to find people posting on Twitter that they love WFH during COVID because it means they get to sit at the beach all day. I've got people on my own timeline that choose WFH because they see it as a chance to slack off without supervision.
A single slacker on a dev team of 5-10 can completely ruin the team's output, and (speaking from experience) it's really hard to prevent, oversee, or correct a slacker situation remotely. You might say "then fire them if they're a slacker", but once you're at the point where you're ready to fire them, the damage and lost productivity has already been done.
The model that I have seen with moderate-to-great levels of success at the large consulting companies (which have long had a strong remote work culture) is that the companies schedule new hires so that all new hires start at the same time every year, and for "new hire training", the company rents out an entire hotel for 2 months and has all new hires stay there. Those 2 months then are a mixture of intensive job training and social events.
By the end, all of the new hires have received plenty of training, had good conversations with managers/leadership about what type of work is expected, and IMO most importantly, have had a chance to make very strong bonds with coworkers that then become your "cohort" for the next 1-2 years that you can ask questions about work, collaborate, commiserate, or even become friends outside of work. The strong bond developed over those 2 months is important because that "cohort" is then more likely to stay in contact even after splitting up to work remotely.
I went through such a training program at the beginning of my career and it was the best company onboarding experience I've been through, not only in terms of personally enjoying it, but also just from the perspective of setting me up for success at the company and in my career.
What skill level is that? For the most part we are talking about a bunch of people ages 22-30 that function by responding to specific feature requests or JIRA tickets from their team leads. There are of course exceptions, but by and large this population of engineers do not do well with unstructured environments, such as the type created by a sudden shift to WFH. I am wholly unsurprised that productivity at Goog has dropped. At my large tech company (where we work with consultants from FAANG) there's also a similar drop in productivity due to aforementioned lack of structure.
>10 years remote and I couldn't get in at Googs.
FAANG interviewing has very little to do with skill level and a lot more to do with mastering the very specific interview process of that particular FAANG. It's a lot like taking the LSAT. You could be a genius but still not ace the LSAT because you don't know the very specific strategies needed for the test. On the flip side, just because you ace the LSAT doesn't mean you are a savant, it just means you studied the specific things necessary to ace the test.
Is this in all of the US, or...?
Water supply is a very localized thing, so comparing water usage in say, Iowa to water usage in California isn't really apple-to-apples. You won't solve California droughts by reducing water usage in Iowa, for example.
>Also note that California produces 80% of the world's almonds, but something like 1% of the world's meat.
If these numbers are accurate, it seems like it's more sensible to discuss almonds in the face of water usage and eschew talking about meat, since California in the midst of its many droughts is specifically using a lot of its local water supply on almonds, not meat.
edit: the numbers I found from a quick Wikipedia search are that 11% of Cali's Ag water is used on pasture forage (though this doesn't necessarily mean it's for meat; from other information on the Wiki page it looks like a lot of this pasture forage is for horses), and 18% on Alfalfa which is exported as cattle feed. So that's anywhere from 18% - 29% on "meat and meat products", whereas 34% is "fruit and nuts" (it's unstated how much of that is almonds).
There's also a huge emphasis in such circles on compensation, and Amazon supposedly has a somewhat lower total compensation for entry level engineers than Google et al. That's a huge deal to status chasers who only measure their self worth in money.
FWIW I do not recommend browsing Blind because it is full of toxic mindsets like that, nor do I agree at all with it... I'm just sharing some context that such communities do exist.
I see this as a huge negative of AWS, personally. While the "freedom" of being able to choose whichever Infra-as-Code tool I personally prefer is nice, it's also a huge negative that there isn't one single tool that has the full backing and endorsement of AWS.
CloudFormation is the "official" tool, but it's basically a second class citizen in AWS rife with bugs and gotchas, and often lags in adding support for new AWS features. CDK is the up-and-coming "official" tool that seems like it might take the spotlight, but it's still in pre-release and because it relies on CloudFormation under the hood, it too is less than ideal.
Terraform is probably the most feature-complete and most frequently updated IaC tool, but since it's technically third party it isn't going to be included in official AWS docs/tutorials or get first party support from AWS.
Then you throw in the other stuff like the Beanstalk CLI, Copilot, SAM, Chalice, Amplify CLI... there are so many tools for creating resources in AWS that it's overwhelming when trying to decide which one to use.
AWS in general follows a paradigm where the target market is generally large, huge enterprises with niche use cases and large IT organizations that don't mind (and often require) taking fine-grained control of things like setting up CI/CD pipelines, deployment configurations, etc. These things are all possible and powerful on AWS but they mostly require self-configuration, which is sort of the opposite of what Heroku/DO App Platform are trying to be.
Beanstalk is in a weird place because it still follows that AWS paradigm of "we want to expose all of these fine-grained controls to the power users at large enterprises" while also still attempting to make it easier for the average developer. The end result is that Beanstalk gets stuck somewhere in the middle.
Beanstalk is a very capable and powerful service, and you certainly can set up a CI/CD pipeline in the way you've described, but you have to set it up yourself using AWS CodePipeline or by using the beanstalk CLI... which is certainly not as developer friendly as something like Heroku, especially if it's just a hobby app that you're toying with on the weekends.
And to muddy the waters a bit more, AWS also has Amplify, which actually does have one-click-setup for a GitHub linked CI/CD pipeline, but AFAIK it's mostly meant for static websites or for mobile apps, so it isn't exactly the same target use cases as Beanstalk.
The pricing model for App Platform seems antithesis to that, though, which is interesting. DO is becoming more like AWS/GCP with every feature release, which I don't necessarily find to be a good thing.
Though I would forgive you for forgetting about EB since it sometimes feels like AWS's neglected step child.