I understand that there was this law. It's a political statement because of the political message being sent out to the user base. The act of shutting down on its own is not a political statement.
716 karma · joined May 16, 2018
I understand that there was this law. It's a political statement because of the political message being sent out to the user base. The act of shutting down on its own is not a political statement.
Political things aside, it's crazy to see so much of a flip-flop so quickly. Has there been any other behavior like this in the past where a company "shut themselves down" to make a big political statement and then almost immediately undid the shut down?
It was nice because I didn't need to practice and I knew exactly how to debug the thing.
It was frustrating because my personal laptop is from 7 years ago (from college), is slow, and the dependencies and editor don't work out of the box for an a new repo. Additionally, I'd prefer to use IntelliJ like I do at work but again, that's too heavy for my computer to handle so I resort to vscode and have to figure out how to use it. So then the interview becomes debugging my environment instead of debugging the problem. Maybe that's a useful signal, but it's not really bug squashing anymore then.
So overall, it was still requiring learning but there was not a very good way to test in advance (how do you test all possible repo structures?)
The reason credit card fraud for charges costs money to processors is because of charge backs. I believe charge back fees originate from the card networks themselves (Visa, MasterCard, etc). These processors also enforce a variety of limits when it comes to chargebacks for each merchant. This means if you're the layer between the merchant and the network, the merchants generally will rely on you to pre-emptively detect fraud. Those systems all cost money too.
As far as I know when it comes to payout rails such as ACH, real time payments (RTP), Zelle, I don't believe the payment processor holds any liability for fraudulent transactions. In other words, if a fraudulent payout occurs through stripe via RTP then The Clearing House banks aren't going to come after stripe for the money. They'll tell the end user "whoops, should've taken better care of your digital info. Bye!"
source: Worked at a payment processor and worked on payout rails and integrating with banks. Also do work now as an end user of a different payment processor that does charging, payouts, etc.
There's definitely some publicly traded tech companies that are missing from the list.
This isn't a ban on companies from collecting personal data. This is a ban for Meta (it's unclear to me if other companies are included) to process user data for the purpose of behavioral advertising.
Genuine question but what's the harm here? Or what's the negative consequence? I understand that this is creepy, people find it uncomfortable or odd, but what about it is harmful or so negative?
Interesting. I wonder what it is for Seattle then.
> The median listing home price in Seattle, WA was $829K in September 2023, trending down -2.5% year-over-year. The median listing home price per square foot was $584. The median home sold price was $799.5K.
Says redfin (https://www.realtor.com/realestateandhomes-search/Seattle_WA...).
Seattle median household income is ~115,000 according to Seattle times (https://www.seattletimes.com/seattle-news/data/seattle-media...). This means that one of the highest earning cities in the U.S. isn't able to comfortably afford a home, even at median prices. So then I wonder how many people are moving into Seattle with high incomes in order to buy homes and such.
It's also very surprising to me that the median home sold price in Seattle is more than New York City.
So over $36k a year. I'm in Washington, so no income tax. Let's say $100k income, single person. No pre tax deductions and you'll be bringing home $6200/mo. So over 50% of your take home goes to mortgage alone.
In your example, your home prices were roughly 3x-4x your annual income. Compared to your example of prices being 5x.
I'm not saying there is no benefit. I'm not saying there is no risk. I agree that going from 8->17 would be worse than 8->11->17.
My point is to list out reasons why a team may not be able to just spend a day upgrading (dependency issues) or why someone might not be given the time to do it.
2) Sure, pushing and making the decision are not the same thing. I can complain and persuade as much as possible and it doesn't mean it's going to happen.
3) I agree that you want people who care about improving software. Upgrading language versions isn't always the best route to do that though.
4) I don't think everyone on the team is reading about the latest updates in the world of Java. I think a pretty small portion of engineers are keeping 100% up to date, following Twitter accounts for Java dev, watching YouTube videos on it, etc. All that is educational and that's great to know but for most people, it's not going to help them work better because they know about features they can't use.
5) definitely sounds aggressive but okay. I haven't found a company yet who's complained about working in Java 8 versus 11/17. If a company is hiring for a role that uses Java, they're likely not limiting their candidates to those who've used their version of Java. It's a pretty standard language and if you know any other object oriented language, you'll be fine.
2) other things are deemed to have higher priority.
3) people are satisfied with existing features and don't want to spend energy to upgrade to something that doesn't provide immediate value.
4) folks aren't educated on what the benefit of switching would be so why would it be prioritized? This is a case of "they don't know what they don't know".
I work on a team using Java 8 daily. It's fine. It's got things I wish it didn't (no null in switch statements for example) but I don't care about that so much that I'm going to go through the pain of upgrading 7-9 services in the mono repo, their dependencies, and then test them all to be on a new version of Java.
right. the law is not to deter illegal possession, it's to deter certain kinds of manufacturing.
> There is no situation in which a criminal could be charged with these laws, where the criminal would not already be facing decadess of prison time for illegal possession of a firearm.
Someone manufactures the weapon and then sells it. If you have no proof of possession you have no case. If you have proof of manufacturing firearms, then you have a case.
Saying "law A should not exist because if law A were broken, law B would already be broken" does make sense if that can be guaranteed to be true, however it's not possible to provide that guarantee, therefore that logic doesn't make sense to go with.
I bet yes. Which means, the laws existence does deter people from doing certain things. It doesn't deter 100% of people, but the percentage is greater than 0.
Background: I graduated from school in Spring 2020 and started at my first full time software in Aug 2020. I've began going to the office about 4 days a week since Feb 2023. Prior to that, I had only been in an office twice ever (excluding my 2019 internship).
Here's some points that make in office tough for me to enjoy.
* When I'm in office, stuck on a problem and need to just think, what can I do? I can stare at other people. I can hear other conversations, others typing, etc. When I'm at home, I can do basic home chores like fold laundry.
* When I'm in office, my lunch options are more limited. I either need to buy lunch, bring it, or select from what work has catered. Bringing a lunch limits options and takes time at home to prepare. When I'm at home, I can eat whatever, whenever. No pressure to sit with people I with with. No comments about why am I eating what I'm eating.
* I typically feel more isolated in the office than I do at home. In the office, I can see others walking around having conversations. I don't know anyone outside of my direct team. Even then, collaboration is very low. With no meetings, I'll talk for maybe 15-20 minutes in the day. At home, I am alone, but I'm not watching others actively socialize. This is more of a me problem than anything.
There are also things I don't like about being in the office in general. I don't like that others speak in languages I don't understand. The monitors, chairs and lighting are worse than at home. The office is in a not great area, and I walk so it's not a nice commute.
Overall, I've come to really enjoy and be excited for my work from home days.
It's also not just my team. I see other tables at lunch and other teams having conversations in what I assume is the same language. I have a hard time differentiating based on sound.
* Occasionally I'll get a good conversation with a teammate or manager about something technical, but the frequency has not gone up. The technical conversations are still scheduled on a calendar and happen at the same frequency. I really haven't experienced many people stopping at my desk and I think I've only stopped at the junior engineers desk to check in.
* Socializing at work has not been my strong suit. I am pretty introverted when it comes to strangers (e.g. anyone who has not been introduced to me). I find the socializing to be more energy draining.
* I walk to work. I like that typically. The walk can be... disturbing to say the least since I walk through downtown Seattle.
* A lot of people in the office prefer to speak to each other in languages other than english. Everyone on my team (my manager + all my coworkers on my team) prefer speaking something other than english and do so unless I'm involved in the conversation. This surprised me and at times I find it frustrating because I wish I could know what they're chatting about when it's technical (certain keywords I can pickup on since they're the name of internal things).
* working in office 4 days a week has given me something to really look forward to each week, and that's the WFH day.
* I don't think my productivity has gone up. Some days it's definitely worse. Now there's an obligation to go sit and eat with others for 30min-1hr a day. Previously, I'd just bring my lunch to my desk and continue to work.
I don't think my experience is the norm. But I certainly miss the pure WFH days.
If I am a service provider, and want to use the FedNow service to power one of my offerings, how can I get started with that?