tossaway9000

The use case seems to be to bypass any value provided in using 2FA in the first place...

Its the same problem just at a different point in time. The latest code introduces the latest bugs and security vulnerabilities too.

I've seen webpack builds larger than this... much larger.

We keep "trying" to rewrite a legacy application, and said rewrite keeps failing, then we end up with what we tried to avoid in the first place: A Frankenstein one-off for some specific project.

A lot of people sing the praise of everything being type safe, but I think the dynamic typing of Php and its synchronous nature are what make it so productive.

Also, at least compared to its C# Frankenstein cousin, uses a fraction of the resources to do MORE work, that still amazes me TBH...

This, you can find some real gems.

I have a pair of big, deep, wooden lacquered coffee mugs (I think they're actually meant for tea or soup) that I got on a trip to Japan. I'd always wanted a wooden mug but the ones I found online were super bulky and expensive, on that trip I just happened to stumble into a store with all kinds of wooden dishware and bought them.

Some of the lacquer is flaking off from use and age (this was probably 6-7 years ago when I got them and I use the EVERY DAY) and I don't want to replace them but find a way to get them re-lacquered, maybe on a future trip back post-COVID shenanigans.

I will happily crowdfund this, and I don't crowdfund anything...

Bunnie did a super neat talk about something similar

https://youtu.be/ruEn7TE4YMM

The Philippines has some special laws on the books to make the country more friendly to outsourced jobs like telemarketing and support. I know there are specifics for foreign PII protection for example, you might want to see if anything exists for IP as well.

Keep in mind that like many things in the Philippines, enforcement isn't very consistent and probably seriousness varies greatly by the region.

I came across a PH goverment website leaking copious amounts of PII and couldn't manage to get anyone at the National Privacy Commission to take it seriously. I lived there for about 3 years.

Since 2016 I've gone through:

1 Macbook Air (stopped booting one day...) 1 iMac (Became unusably slow) 2 Macbook Pros (One stopped booting, one had keyboard issues and a swollen battery preventing the lid from closing)

and am on my 3rd Macbook Pro now which is plagued with the keyboard issues...

Meanwhile I have an E500 Thinkpad from 2011 that still runs like a champ and has been abused more than any of the Macbooks.

I'm not buy any more Macbooks to say the least...

Azure is also _down under_ in Australia!

I'll see myself out...

I suspect those going into video game design programs have a similar success rate (if not worse.)

430+ repos here, corporate setting, its not great but we use some custom scripts (validate users, groups, which repos are allowed to be public), strict documentation, and quarterly auditing. We have a lot of strict requirements around branch protections and the API for branch protections leaves a lot to be desired.

We've found that setting up new repos in a strictly documented manner has been the best way to approach it, we also have some github actions that run periodically to run some sanity checks across repos.

We're a terraform shop but we had countless issues with the terraform-github-provider but, maybe its improved the last year or so.

Also, Github has no "protections" around tagging, this really hurts us as we want to move to tags and releases for versioning but don't have a way to require multiple approvals before cutting an artifact that can be promoted so we have to wrap some customization and processes around it.

The worst thing about this will be all the discussions that you will miss out on that everyone will assume you know.

Several years ago I was the first and only remote person on the team, and often would find myself with an assigned task with no details, or "talk to so and so", even worse would be working on a story only to find out some implementation detail changed and the response was "oh, we talked about that the other day". This was magnified 2x when I was also working in a significantly different timezone.

In 2012 or so we doubled down on jQuery UI, specifically the widget factory and a few dozen custom widgets extended from a custom parent widget. That application is STILL in production today, chugging along in both the private and public sectors.

Page 5 at least settles one debate. BIRDS AREN'T REAL, they're just "Airbone Clutter"

> Airborne Clutter: These objects include birds, balloons, ..

Oddly enough, my wife started having problems recently connecting to our network on her iPhone. The access point name is an emoji (and is also a hidden SSID) it doesn't totally break WiFi but it recently started to refuse connecting just saying "Unable to join".

I don't hate Javascript, I actually like it for quick scripting and data-mangling. But I DO hate the never ending bits of syntax sugar added on top that I rarely actually care about. Also tired of people constantly inventing reasons to compile things INTO JavaScript (e.g. Babel, TypeScript, CoffeeScript).

Thanks, that worked, if I had not seen this message I might have forgotten about this and never returned.

Got "Unauthorized" message when trying to sign up, switch to Chrome (was using Firefox) then said my email was in use. Tried to reset but nothing happens (console errors showing 401 errors).

Just me or did Hackernews hug the site to death?

Maybe post a review on Glassdoor?

I moved out of a SWE role into SRE role a few years ago, then into SRE management role.

This is my experience, YMMV:

Pros:

1. Get to do a variety of things, not stuck writing business rules in one particular language.

2. Paid better than most if not all of the web developers in our division.

3. Feels like a stable role at the moment. Hiring replacements has been difficult so company has made some effort to keep our team happy. We've survived an initial COVID staff reduction.

Cons:

1. On-call rotation and having to support code you didn't write (especially if it turns out to be of poor quality) can be frustrating.

2. I'm finding it hard to pivot into a development role again, after not having done full-time development in a few years. Both finding the time to catch-up and not getting great responses for applications I send out to other companies.

3. Working with one particular cloud provider isn't challenging. I don't feel like I'm learning any actual skills, just "the way AWS would like you to do things".

4. A lot of the CI/CD, Configuration management, and Infrastructure as Code tools feel like they're still in the dark ages (hey let's just add templating to YAML, it'll be great /s)

Aside from being female that sounds a lot like me.

I don't want to do programming interviews. Things that normally come easy to me feel impossible during live coding interviews.

Not everyone wants to be a pair programmer.

Not everyone wants to have their own live coding youtube/switch channel.

Start off by saying that the goal of the post-mortem is not too blame anyone or point fingers but to find out where improvements can be made and where downtime and incidents can be reduced. Every time a team is paged at our company we have a post-mortem meeting to review the incident. If we have a lot in a specific week we do them in batches when possible. We pull in anyone involved with identifying, triaging, or resolving the incident and create follow-up tasks based on the meeting. You might want to try the Five Whys approach as well: https://en.wikipedia.org/wiki/Five_whys

Yes it makes me really annoyed and is definitely a contributing factor for why I'm still at my current employer, I lose all hope after reading a couple. Skimming past the bullshit only goes so far. It would also be great if I didn't have to go to a third-party source to find out what their hiring process looks like. I have little interest being grilled over a whiteboard when I'm not even sure if I want to work at the company yet.