akatechis

Jokes on us, the "east coast kids" already fly to israel on our dime...

As a greek speaker, thanks but no thanks. We don't need a 9% compression revision in our language.

Όχι

> the CIA report predates the attack, which is especially strange

It's only strange if you believe the CIA released notes from their super-secret psychic program rather than the more plausible explanation that this is disinformation that was backdated for a boost of prestige.

I've been working in this field for about 15 years, mostly full stack but focus on frontend. In the past couple of years I've been making this transition from individual contributor/senior developer to a team lead and manager role.

For me, what has worked CONSISTENTLY are 3 things:

1. Take initiative: I can't stress this enough. If you act like a team lead, people will recognize you. And if they don't, you should consider whether this is somewhere you want to be. An organization that doesn't help build its talent, is not one where you will accomplish your personal growth objectives.

2. Speak to your Manager: Assuming you are doing #1, make sure that your manager(s) are aware of your career goals. You need to get "buyin" from others in the organization that are able to carve out this kind of role for you. They will also have good advice for you. Not every manager/team lead role is the same, so YMMV in this regard. It may be that there's a bigger need for a people manager vs a technical manager.

3. Stay at a company for 3+ years: The number might be different, but in my experience this is the point, after which you have been around enough time to have been involved in many different projects. Not only will you know a lot of the tech stack and it's limitations, you will also understand MUCH of the business itself. You'll have positioned yourself at the intersection of the business and the technology, and become an indispensable part of the organization.

One of the companies I worked at was a personal finance startup, and over the years I learned so much about saving, spending, credit, loans, income and investing IN ADDITION TO the technology we were building and everything that was powering it, that I was asked to be a part of nearly every discussion.

A lot of companies do this just as a matter of course. They call it "trimming the fat", eg, laying off the bottom 5%, 10% or whatever percent of employees, in hopes the future hires will be higher performing.

Just another person mad at Elon lol

> Maybe then people will learn you don't get to sit there spouting blatant lies without consequence.

That is partly true. The ruling class gets to lie with impunity whenever they want, for profit or power. Remember WMDs in Iraq? And Iran has been "6 months away from a nuclear bomb" for the past 50 years.

It's quite sad that "Build your own frontend framework/library" is just a bunch of "Build your own React" links...

The "edge" didn't really exist at the time, along with concepts like cloud, serverless. I seem to remember that even CDN was an evolving architecture idea at the time.

AWS et al had not yet turned web servers into a commodity, so it wasn't feasible to "just deploy the software to multiple regions" to improve latency.

The glow in the darks got him... :(

And yet, abortions continue to be legal everywhere. It's almost as if, the supreme court is there to just rubber stamp what the elite class of our country already dictates.

This is absolutely untrue. When you look at the political landscape, evangelicals have no power. And yet, when you look at any vote in Congress regarding Israeli issues, such as the recent vote to replenish the Iron Dome system, it was overwhelmingly voted in. The only "controversy" was the 3 or 4 people who objected initially, and were then bullied BY BOTH PARTIES into voting yes.

> The second rule of SPAs: we always underestimate the complexity of reimplementing history and link navigation. Often by a large margin. But we get away with not caring because nobody tests history management properly.

Exception to the second rule of SPAS: Users will always test your history management properly.

Is this news?

Just build your own internet, financial system, and government, goy.

This reads like all the other "white supremacist" plots. A group of FBI agents, working overtime to convince a mentally ill, unstable, or young and impressionable person to carry out an attack he would not be able to otherwise execute on his own.

In a just country, where the rule of law applies, this would easily be classified as entrapment.

Can't remember the times I've had to google "Pop commit and move to another branch", for when I accidentally commit to `master` when I meant to commit it to `feature-branch`...

Is this supposed to be a touch/pen interface first? I'm trying it out with a mouse, and having many issues, like drawing of random lines as I draw, as well as losing lots of draw operations when it does a sync with the server.

As bad as it needs to be.

No. I got my money in my account yesterday, about an hour after my employeer direct-deposited my paycheck.

> These banks' IT systems are storing things that many of us would argue are much more valuable than your passwords. A bank's core system also represents the actual monetary value of every customer's account. We are talking about password security in a system domain where there are arguably far more valuable assets to secure.

The password is what secures the more valuable things inside the account (the money). In fact, in nearly every case a password is used, no one really cares much about the password itself, but what's inside. That's why services require password in the first place.

EDIT: Also, don't be so sure that passwords are not useful. If you can compromise a password in one service, there is a significant chance that the user in question is re-using the same password on other (or all?) services. If your password is "joe123" on somewebsite.com, if I can crack that, I can try to use that information to guess your login on somebank.com, somedoctor.com and somegovernmentservice.gov. The more things become "cloud"-based, the higher the value of cracking a password.

I think the bigger consideration is actually how to exfiltrate money from an account that you compromise: If you initiate a wire transfer to some account you control, that leaves a paper trail, and typically has a lag time, during which the institution/customer have a chance to react. This is also why scam centers in India ask you to send them cash equivalents: gift card codes they can redeem/resell.

By technobabble do you mean all the tech companies that claim they are "changing the world" by whatever it is they are doing? I've seen so many "content platforms" that claim to be "revolutionizing" or "democratizing" or whatever other buzzword you like, access to data, when in reality, they're doing no such thing.

Anyone else having issues with this link in Firefox?

> An error occurred during a connection to conferences.sigcomm.org. SSL received a record that exceeded the maximum permissible length. Error code: SSL_ERROR_RX_RECORD_TOO_LONG

There's also PureScript snicker

What I don't understand is the math. Author makes the claim that using 3 words changes the combinatorics from 62^12 (62 characters, in 12 positions) to 20,000^3 (20k words, in 3 positions) but a hashing algorithm doesn't work with words, it works with characters, so if the words are 4 characters each, you've still got 12 characters to fill. Since an attacker doesn't know that you've not used symbols or numbers, they can't reduce the problem space to 26^12. Right?

Have I missed something in the article that would make the connection?

EDIT: Yes, hashing works with bytes, so technically, it can be even stronger if we include charsets from other scripts in the problem space.

Exactly. At an investment bank for which I used to work in NYC, they moved their datacenter to be next door to the exchange's datacenter just to reduce latency.

Because in HFT, every fraction of a second can mean the difference between 10s or even 100s of millions of dollars in profit/loss.

Google (and any MegaCorp) will siphon out any love you have for your profession. Go startup.

The difference is that JS has to be backwards compatible in order to not break 50% of the internet. With PHP, it is theoretically possible to make a major version upgrade that fixes most if not all the issues without worrying about breaking backwards, since upgrading is opt-in.

We use ProGet with npm, docker and nuget feeds. We only ever hit the internet when we install fresh dependencies. After that, they get cached on our local service for all developers and machines to consume. That, coupled with yarn itself, which caches dependencies locally as well so subsequent installs don't even go out to the network, has accelerated our build times considerably.