Fernando Flórez

@CarlosCornejoA @RafaelRGA @larepublica_pe Al comprar la máquina también le pagas el sueldo a empleados (que crean, mantienen y soportan las maquinas).

Esta máquina cuesta 8,300 USD (S/.28,220.00). El hardware está en los 5,000 USD unidad (Toshiba o NCR). El software más licencias anuales 3,000 USD máquina. El mantenimiento anual de lector de código de barras 300 USD máquina. Solo una máquina pagaría 20 sueldos mínimos, casi de 2 años de un joven en un trabajo formal con todos sus derechos. También lo puedes ver así. Si por cada máquina al año el supermercado se está ahorrando S/.16,921.33 al año al no pagarle al trabajador y te hace a ti hacer lo que ese trabajador hacía, ¿por qué no te hace un descuento? Te has convertido en su esclavo donde te utiliza para sumar sus ganancias. Ahora tú embolsas y tú eres su cajero, y te creíste el cuento.

En #QueNoSeTeOlvide continuamos con nuestra campaña "Dile NO al autoservicio". Demórate 15 minutos en la cola esperando que te atienda una persona, pero no le quites trabajo a la gente joven. @larepublica_pe

@fluffypony @R0bAley @CardilloSamuel @levelsio IF the HSTS header is there. You are thinking on a well configured web but that doesnt mean thats the case always. To have your credentials hijacked via mitm is very unlikely but not impossible. Isnt cert pinning not recommended anymore btw?

The amount of absolute nonsense in this thread…HSTS and the preload list prevent this in browsers, certificate pinning prevents this in apps. Even absent that, no app is going to accept a self-signed cert for a backend connection, and browsers make you jump through hoops when trying to connect to a page with a self-signed cert.

Your email wasn't hacked because of an unsafe WiFi HTTPS is fully encrypted You were hacked for some other reason like no 2FA or having some malware running on your device Nothing to do with whatever WiFi you were on

@R0bAley @CardilloSamuel @levelsio Compromised networks could trick you to accept a self signed cert

@CardilloSamuel @levelsio what do you mean? in a mitm scenario the attacker will only see encrypted traffic unless the encryption is somehow also compromised

Verifying myself: I am fernandoflorez on Keybase.io. 45UOIAg3U48wyRhGRHtIsEgYH0pq9MBW0UpW / keybase.io/fernandoflorez…

@alexisohanian @kevinrose @digg Digg3.0 . We all remember digg2.0

@kevinrose @digg Digg 1.0 was "the homepage of the internet." A place to be with humanity and connection at it's core. Digg 2.0 will build on that promise, using AI as a powerful unlock to make community moderation suck less, user support better + all-in-all make social media fun again.

The early web was fun. It was weird. It was community-driven. It's time to rebuild that. Which is why @KevinRose & I just bought back @Digg — rival CEOs turned partners! Just don't call it nostalgia! This is a necessary evolution.

@mitchellh Its because of the hype and that it is not really cool looking if everyone and the youtube kid is using it. I like it overall except for the config format. Great work!

Ghostty on Reddit, there's a lesson in this. 🤣 "r/macOS": Neat, nice app. iTerm is nice too. I love choice. "r/linux": arguments about what "native" means, angry they have to click one link to learn what it is, disappointed that another terminal exists, 50-comment discussion about GTK vs QT

@apenwarr @nuonjon @Tailscale @nuoninc Following the post example use, it would be great to use tailscale as an sso for a funneled url. Could be done now but all users will be inside the plan which will count as active users. Can we have a $1 a month plan just for auth through tailscale per user? 😬🙏🏼

@fernandoflorez @nuonjon @Tailscale @nuoninc Are you thinking of node sharing or something else? tailscale.com/kb/1388/inviti… Maybe Tailscale Funnel?

So much admiration for @Tailscale, I think they are one of the highest bar in terms of software craft. Been waiting for a good reason to justify moving @nuoninc over, and low and behold.. they shipped Serve tailscale.dev/blog/id-header…

What @Adobe is doing to trick users into annual plans by offering free trials is crazy!Even when you get a monthly plan,the trial is on an annual commitment. They are also separate plans so If you cancel what you actually purchased,you need to make extra steps to cancel the trial

If you use tmux and @Tailscale check out my first tmux tpm plugin to display tailscale’s status on the status bar github.com/fernandoflorez…

Crazy all mentions are to fb or ig being down and everyone forgets about threads

Like if you remember WDDX

@dmwlff @Meta @reactjs @threadreaderapp unroll

I ended my time at @Meta as a director. But I started as an engineer on FB Chat. Everything about it was broken — we had to rewrite it. And while the effort to fix it is one the projects that led to @reactjs, the most important fix was far simpler... Here’s the full story: — I worked on Facebook Chat for several years, both on the front end and the infrastructure. Before the major effort to redo the UI, FB Chat was super broken and we had no idea why. We got tons of bug reports about Chat being broken every day, but we noticed an odd pattern in the data: the volume of reports didn’t match the volume of usage. It was time-shifted from the peaks we’d see in the US. We didn’t know what was wrong, but we knew the code was a mess. We set about rewriting both the front-end and the back-end in an effort to fix it. The front-end rewrite pulled in a whole team of amazing engineers and became one of the big threads that led to @reactjs In the public eye, we portrayed this project as the one that ultimately fixed Chat. And the way I’ve usually told it, fixing Facebook Chat and the birth of React are the same story. But no framework was going to fix the worst problem with Chat. — During the time we were working on the Chat rewrite, we were also replacing the original Erlang backend with one written in C++. This was probably a good move, but the problem wasn’t with Erlang either. Our initial spec for the new backend didn’t say much about observability, but it was an important feature, and the rewrite forced us to rebuild it. Little did we know this would lead us to the root cause of our problems… When we finally gained insight into our deliverability data, we were able to cut it by region. We noticed Chat was really popular in India. This was before WhatsApp, at a time when SMS wasn’t reliable. Eventually we pinpointed a region in India where one specific DNS provider was giving out the wrong IP addresses for our Chat servers. So when people went to use Chat, they would sometimes get a notification that they had a message, and then it would disappear. Or they’d send a message and it would get lost. All because they were connecting to the wrong IP address. That was it! None of the sexy new tech we were working on was going to solve that problem. Ever. — Instead, the solution was to build observability that allowed us to track end-to-end message delivery. In the end, we could start with a broad cut of our data by country or web browser, and then zoom all the way in to look at what happened to a specific message for a specific user. Once we pinpointed that the problem was with a DNS server, the matter was resolved with a quick phone call. I don’t know what they did, but I imagine it was something like turning it off and turning it on again. We sometimes talk about observability as if it’s enough to buy a product like Datadog and just look at the pretty graphs. Sure, that’s a start. But true observability is a feature that needs to be built— painstakingly, iteratively, by-definition starting with a shot in the dark. — These days, it has become fashionable to poo-poo the idea of being data-driven. People point out that measurement can distort the phenomenon that is being observed. They want to make processes “data-informed.” But this seems like silly backlash against the only rigorous standard in all of software engineering: That we hold ourselves to an objective standard. We measure how long things take, how many errors we encounter, how often a process successfully runs to completion. So here’s what this experience taught me about observability: When an issue happens in production, time-box the investigation. Sure, take a few hours to try and figure it out by looking in the logs and inspecting the code. But if you’re coming to the end of the day and you still don’t have a fix, then push a PR that adds logging. The first one may be just a guess, but it will begin a process that leads to the truth. And that is what we should all ultimately be striving for. — For more engineering tips and stories, follow me @dmwlff

@jesterxl Yes! It is always great when this happens. Now with remote work it requires some extra time to correctly mentor but it is satisfying. Now with so much online courses it is “rare” to find a new dev looking for jr positions though

Getting a junior on my team, fuck yeah. The kid is smarter than me, fuck yeah.

Been a fan of @astral_sh ‘s ruff so it is no surprise this is so fast

After an hour playing with @mitsuhiko ‘s rye I can say that it is great. Wish syncs would be faster for big projects (it does diff syncs?) and that you could init it in bare mode (—no-lib?) so I could migrate existing projects

Kinesis advantage 360 pro, glove80 or voyager? Whats the best keyboard out there?

@cainux @gitpod @paw_lean Whats this?

Thanks for the swag! @gitpod #gitpodlondon @paw_lean

@jesterxl Also not to be confused by github pages ;)

AWS Copilot, their CLI for ECS, which is managed EC2's and Containers, not to be confused with Github Copilot, Microsoft's AI code hint helper, now has the ability to deploy Serverless using S3 & CloudFront. The. Fuck.

@cesars Depende de a que persona del área comercial le preguntes. Podría ser una nube privada con super baja latencia™️

Ok, rack+servidores es un datacenter.