Jon Peck retweeted
AI is reshaping DevOps – but how do you scale smarter, faster, and more responsibly?
At ODSC AI West, @peckjon, @github, will share real-world strategies in his talk:
Scaling AI-Driven DevOps: Smarter, Faster, and More Responsible Workflows.
Register → hubs.li/Q03Q034q0
Jon Peck retweeted
We’re thrilled to welcome @peckjon (@GitHub) to ODSC West 2025! 💻
If you’re building AI-powered developer workflows, or want to see what’s next for AI + DevOps at scale, Jon’s insights will be invaluable.
Don’t miss out! Register now -> hubs.li/Q03CNZ9B0
Jon Peck retweeted
GitHub's @peckjon & @ladykerr built the same app 3x using GitHub Copilot: GPT-4, Claude 3.5, & Gemini 2.5
What they learned:
– Prompt > model size
– Agent mode is 🔥 but needs oversight
– Custom instructions = underrated
Full demo: github.blog/ai-and-ml/real%e… #GitHubCopilot #AI
Jon Peck retweeted
We got to see 5 incredible devtools demo AI live at Dark Mode ⚡️
The end of README, an AI app built in 5 minutes + more!
Now ready for you to watch 🍿 jam.dev/blog/ai-demos-from-d…
Jon Peck retweeted
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!
Jon Peck retweeted
Tired of clicking the "close" button on every GitHub Issue? Now GitHub Projects will do it for you! ✅
Learn how to use the new "auto-close issues" workflow for automatic single- and mass-closure based on item status. ⬇️
Jon Peck retweeted
Replying to @molly0xFFF
Information density.
2000: search for (topic). Click first result. Read for 15m. Know everything about (topic).
Now: search, skip ads, open next 5 results, close half that are spam, skim past the ads and clickbait and SEO filler to get maybe 3 sentences of info
Jon Peck retweeted
Check out the latest #GitHub product updates from my colleague Dhana!
⚡GitHub Copilot for Enterprise
⚡GitHub Advanced security for Azure DevOps
⚡GitHub Enterprise Importer
gh.io/whatsnewforisvs
@github #GitHubActions #GitHubCopilot #Azure #Devops #AzureDevops
Jon Peck retweeted
ppl keep asking me how we can get more women into neteng so i just made a commercial for it. sexism in tech is now solved you’re welcome
Jon Peck retweeted
Riven is a really great game. It's maybe the single most immersive game ever made, which is impressive, given it's 25 years old and is presented in a manner only slightly more interactive than a powerpoint presentation — at a 640x480 resolution to boot.
Let me sell you on it.
Jon Peck retweeted
Today, we are thrilled to announce the GA of the new Projects powered by Issues, giving you and your team a flexible way to plan directly in the work you are doing on @github! 🎉🗓️
It’s here! 🎉 Powerful, customizable project planning next to your code is now available to all. Try it out today and let us know what you think. github.blog/2022-07-27-plann…
Jon Peck retweeted
The most important skill you’ve never been taught:
Storytelling
10 dead-simple tips to make you a better storyteller:
Jon Peck retweeted
My parents have made it to Poland after walking 15 km for more than 20 hours. They are now being transported to Warsaw and will fly to Ireland next. If someone has experience with asylum seeking process here - let me know. – at Dublin City, Ireland
Jon Peck retweeted
🐍 Am loving this tutorial from @jeremyphoward, which shows a Python-based way to create and orchestrate @github Actions:
ghapi.fast.ai/tutorial_actio… – at Seattle, WA


























