Zetaphor @ Zetaphor @zemmy.cc

Developer, 11 year reddit refugee

---

Read more

Posts

7

Comments

148

Joined

1 yr. ago

I'm curious, why bother with multiple accounts? It seems counterintuitive when taking federation into account

Edit: All of these reasons are why I host my own instance

There's a lot of little things like that, that are very different here and we just take for granted without thinking twice. I'm in Argentina and have noticed a ton of stuff like this.

A random example is there's a handle next to the stove where you close the gas line when it's not in use. They don't just have an always on supply of naturals gas ready to leak from the burner if you accidentally twist the knob.

Another one is the freezer will seal itself shut for about 15 seconds after being opened. I thought it was broken the first time I experienced this and tried forcing it open.

Also all of South America. Everything from ordering pizza to scheduling a doctor's appointment. Not having WhatsApp means you are not able to participate in society

You say that as though there's some kind of crystal ball we can all look into and see all of the obstacles that will need to be cleared and prepare accordingly. That's not how scaling web services works, especially distributed ones that are built on a relatively new protocol.

A lot of armchair developers in here who think there is an easy solution to distributed identity

Who was the idiot

The W3C, also known as the people who develop the web standards. It's a reasonable expectation as you have to draw a line in the sand somewhere. Distributed identity is not a solved problem, so domains are the best solution we have right now.

What would you suggest they use as the identifier with which allows other entities uniquely identity you? There are no alternatives until you introduce a ton of cryptography, which is what DID hopes to address, but that's still going to be bad UX.

That entirely depends on the employer, but in my anecdotal experience that has been the case. Especially in more recent years versus the start of my career (nearly 20 years ago).

The reality is that Computer Science is useful for building strong engineers over the long-term, but it doesn't at all prepare you for the reality of working in a team environment and contributing code to a living project. They don't even teach you git as far as I'm aware.

Contributing to open source demonstrates a lot of the real-world skills that are required in a workplace, beyond just having the comprehension and skill in the language/tool of choice you're interviewing for.

Looks like it wasn't just you, a bunch of large instances just had an outage

Just a heads up, you replied multiple times to this. If the client you're using doesn't submit immediately, that just means it's not doing error handling properly and not disabling submit buttons while the request is in flight. You've actually submitted once for each time you pressed the button

People should be attacking your idea, not their perception of you based on your choice in browser.

My objection with Brave, Vivaldi, and other other browser that is just Chrome with a different skin of paint is they are all signalling an acceptance of Google's monopoly over the web standards ecosystem.

Mozilla is a shit organization run by a shit CEO, but they're the only alternative we have to the megalith that is the advertising company known as Google. It really shouldn't be a hard argument to understand that putting an advertising company at the head of the web standards process is a really bad idea if you care about anything other than Google's revenue streams, ie a free and open web.

Chromium only exists as a way for Google to keep antitrust regulators from coming after them like they did to Microsoft when IE had a monopoly. It's source-available, not open source, they don't accept commits from non-Googlers. The moment they feel safe closing down the Chromium repos without having to lose too much money in fines or blowback, they absolutely will.

We're literally watching this happen right now with Android, another formally open source project from Google that is slowly having all of its open source components clawed back so that they can maintain their control over the ecosystem and protect the revenue stream that is their data collection and app store.

When Google inevitably decides to pull the plug on Chromium the collective of forked browser developers is not going to be able to keep up with the massive engineering effort required to keep a modern browser going. Especially when a corporation like Google can and will push forward complex and difficult to implement standards expressly for the purpose of making those forks obsolete. They have the manpower, capital, and control over massive web properties to effectively push out anyone they don't want.

All it takes is them making a change to Youtube that hinders alternative browsers and that will be the death of that open source ecosystem. They've literally pulled this exact move before with Youtube by hindering Firefox's performance by pushing through the implementation of shadow DOM.

All of this has happened before and all of this will happen again. Trusting an advertising company with control of the open web is the nerd equivalent of leopards ate my face

I surely deserve death for using a browser you don’t like.

I'm not sure how you managed to come to that conclusion. You claimed Firefox is a poor choice, I'm demonstrating why I believe your alternative choice is worse. Nevermind the fact that use of Chromium is effectively an acceptance of Google's monopoly over the web standards, which is the point we're all arguing here. If you can't handle criticism you should reconsider making such hyperbolic remarks.

Username checks out

Nothing about this is recent, those who pay attention to the standards process have been screaming for ages about the Google problem. It's just that now between interest rates being what they are and them having a monopoly on the browser market that they're cashing in on their investment.

It's Brave, as evidenced in their history. The browser that peddles crypto ads, has a transphobe CEO, and has been accused of selling copyrighted data

For sites that rely on XHR using Javascript, which let's be honest is pretty much all of them, this would not work due to CORS and CSP restrictions

Build an open source portfolio. Being able to show employers what I was capable of was a massive benefit both then and now. You can say you know all of these things, but when you're looking at hundreds of applications one of the first things they do to reduce the pile is filter out people who don't have some kind of online presence like Github. This allows them to see that you're actively engaged with the field and if they want to interview you, to look at your code quality and experience.

A personal website that highlights your best work is also a good idea, as it helps to even further distill down the things you're ultimately going to end up talking about in an interview. It doesn't need to be anything fancy, just something that shows your competent. I wouldn't expect the person interviewing you to actually hit view source and criticize your choice in frontend framework.

I was interviewed with complex logic problems and a rigorous testing of my domain knowledge.

Most of what I do is updating copy and images.

This is also just the reality of the job market, especially in this industry. Dev positions get hundreds if not thousands of applications which all vary widely in quality.

I have 20 years of experience and a six figure salary, the last time I went looking for work and was putting out applications I sent out easily over 100 applications and only had 4 interviews. I've found it's best to form a relationship with a competent recruiter, and work with them anytime you're back on the market. They're incentivized to find you a decent position so that they can make their commission. Of course finding one that is decent is almost as hard as the process of sending out applications, but once you do it's a relationship worth maintaining.

I've never been to college and my job title today is Software Architect, I've been doing this for nearly 20 years.

It was extremely hard at first to get a job because everyone wanted a BA, but that was also 20 years ago. Once I had some experience and could clearly demonstrate my capabilities they were more open to hiring me. The thing a degree shows is that you have some level of experience and commitment, but the reality is a BA in CompSci doesn't actually prepare you for the reality of 99% of software development.

I think most companies these days have come to realize this. Unless you're trying to apply to one of the FANG corps (or whatever the acronym is now) you'll be just fine if you have a decent portfolio and can demonstrate an understanding of the fundamentals.

I certainly experienced this at the start of my career. Everyone wanted me to have at least bachelors degree despite the fact that I was able to run circles around fresh college graduates. It wasn't until someone gave me a chance and I had real world experience that people stopped asking me about my college education. In fact later into my career when they learn about the level of experience I have and that I'm entirely self-taught, it's often seen as something positive. It's a shitty catch-22