Current iteration: Director of Engineering @StreetEasy (Zillow) • Previously: Director DevOps & Data @BlueApron • Co-founder & CTO @ Piictu 🦣 @edgar@toot.io
New York, NY
Joined March 2007
- Tweets22.8K
- Following721
- Followers3.1K
- Likes2.2K
@JessyCarrillo live en este momento conversando sobre la audiencia de Maduro y Cilia hoy
En #NocheD, Jessica Carrillo Mazzali dice: pareciera que la actitud de Maduro y Flores en el juicio es parte de esta estrategia de la defensa. De lo contrario no se entendería por qué la actitud desafiante con el juez.
xitter.twitterapi.xyz/i/broadcasts/1yNxabBEq…
1
688
A shameless plug
Si quieren estar al tanto del caso de Maduro y Cilia en NYC, sigan a Jessy.
En su momento ella cubrió el caso de los narcosobrinos.com
@AKurmanaev it doesn’t seem like you’ve lived 8 years in Venezuela. How could Delcy be described as ‘the moderate’. The SEBIN— responsible of killing and torturing political prisoners— reports directly to her
Hard to see this analysis as being made/edited in good faith @nytimes
If Maduro goes, who would replace him? nytimes.com/2025/12/05/world…
Readers added context they thought people might want to know
The article mentions RodrÍguez as a moderate. However, she is a far-left Marxist accused of human rights violations and is directly responsible for the humanitarian crisis as a VP.
bbc.com/news/world-lat…
en.wikipedia.org/wiki/Delcy_Rod…
343
NIST is updating their password guidelines, finally getting rid of
- password rotations
- complexity rules - adopt phrasing instead
Please share this far and wide. As far and wide as you can. NIST Password Guidelines for 2024 are in the process of being updated.
This is a HUGE pet-peeve of mine (when vendors in particular are still operating like its 2017 and keep changing passwords every 60 days, STOP DOING THIS, it's outdated and has been shown to put you MORE at risk than less -- NIST explains why it does in this document, meticulously outlining user behavior**) so I'm sharing this in the hopes all of you will pass it along to your bosses.
The Special Publication series governing passwords is SP 800-63 "Digital Identity Guidelines".
The 2024 version is 800-63-4.
Here: pages.nist.gov/800-63-4/
The companion docs are also on that link. They are 800-63A, 800-63B and 800-63C. These are different documents for different scenarios in play at your org.
The previous update was in2020.
The changes in the 2020 version from the 2017 version were numerous but one of them was that the password verification method should NO LONGER require passwords be changed at specific intervals (i.e. every 60 days) but in the following circumstances instead:
1. After a breach/compromise
2. User request
2024 repeats this and adds a bunch more guidlines but here is a screenshot of page 13 of the new 800-63-4 (note the # 4 after it) which outlines how your systems should now and moving forward, be handling passwords.
This goes for Active Directory, too. All your systems which have passwords should align with these guidelines provided there isn't another standard or framework you must adhere to which overrules this.
Most frameworks, however, have moved away from arbitrary password resets and complexity rules.
**We cybersec researchers and hackers use wordlists from breaches in a variety of different ways. Hackers use them in tooling to crack passwords whereas researchers use breach dumps to see the kinds of passwords users are creating and the psychology behind them.
Using complexity rules gets you the user psychology of:
Password1
Password2
and so on
Use phrasing instead and allow for spaces, which is important. Humans type phrases with spaces. They also mention phish-resistant methods and most vendors are on-board with MS going to be turning off all Legacy Auth next month, across all free accounts and tenancies.
I'm so excited for the new changes!
Ok I'm off my soapbox.
Share the love! Thank you!
From the Carter Center
(who in the past validated the results of several processes that declared the Chavismo winner of the elections)
El nombre del dominio es la merma, y además está hosting un fork del código de @ielijose para acceder las actas.
Pura creatividad y talento. Maravillosa sinergia 🇻🇪
Esto 👇
También a la orden por acá
DE PANA, si alguien conoce al equipo que está armando la página de resultadospresidencialesvene… y necesitan apoyo de ingenieros super top que en su día a día manejan de forma rutinaria millones de requerimientos y ataques DDoS mis DMs están abiertos para echar una mano con lo que sea.
3
1,267
theregister.com/2024/01/04/n…
Wirth was one my CS heroes, I used two of his languages: PASCAL and MODULA
He made enormous contributions to the field of Computer Science
Yeah, everything in JS is an object …
but still #wat
![JS snippets from Chrome console: let items = [1, 2, 3] > undefined items[0.5] = 1 > 1 items > (3) [1, 2, 3, 0.5: 1] items.length > 3](https://pbs.twimg.com/media/F8_IR1iasAAr4_E.png?name=orig)
Interesting post 👇
I wrote a piece on the challenges of staying on top of things as an engineering leader + a lil' update on what I've been up to:
philcalcado.com/2023/07/21/a…
17
25
2,610
Generative AI is potentially harming itself platformer.news/p/the-ai-is-…
¯\_(ツ)_/¯
Effective Java is banned in Ohio prisons! I am not making this up. Thanks to @Cidmonster and the @MarshallProj for their fine investigative reporting. themarshallproject.org/2023/…
1
1,239
“Just as one can thoughtfully and responsibly use financial debt to accomplish goals, one can use technical debt to do so,but it is critical to do so thoughtfully and responsibly.This isn’t a new idea.This idea is central to Cunningham’s original metaphor” ieeexplore.ieee.org/document…
1
848
That code you delivered today is already legacy
If you're a software engineer, your main job is maintaining legacy code.
Why? Because building a system doesn't take long, in comparison to how long code will last, assuming the code/business are successful.
Here are the 10 commandments of maintaining legacy code.
🧵
1
794
"Slack is the policy of deliberately leaving time that isn't allocated for stories, using that time for unplanned work. Although this seems inefficient, it usually yields a significant improvement for the productivity of a team ..."
NEW POST: Many software teams pack too much work into their iterations. Teams will usually run better when they have deliberate slack, as it allows their delivery to be more predictable and gives them time to improve their environment.
martinfowler.com/bliki/Slack…
1
687