I have CI on a readme.md file. Today, that CI randomly broke because a link went dark. I got notified, fixed it, and it was up and running again in an hour.
R. Jason Kerney retweeted
Tech interviews have ruined our industry because the most valuable skill is algorithms, since that enables you to quit toxic companies and pass new interviews.
So we never master architecture, soft skills, and empathy - which creates the toxicity we’re running from.
R. Jason Kerney retweeted
#agile2023 attendees, come and experience Your First TDD workshop on MONDAY afternoon. POs, send your programmers. Hosted by @jlangr and me, with help from awesome coaches @tottinge @JonKernPA @LlewellynFalco @JasonKerney
@AgileAlliance
R. Jason Kerney retweeted
I hope to see you at #Agile2023. Jeff Langr (@jlangr) and I will guide you through Your First Test-Driven Development. We'll have great coaches to assist in the exercise (@JasonKerney @tottinge)
Business people, don't forget your developers!
@AgileAlliance
R. Jason Kerney retweeted
Kind of curious. If you do Scrum or some other Agile™ methodology/framework, what exactly does it buy you? What was your goal when you adopted it? Did it move you toward that goal? In other words, why?
R. Jason Kerney retweeted
Some people asked me to share what I just shared in a space about the rate limits. I don't work for Twitter but, I do architect IT cloud solutions as my day job.
It is temporary. Twitter's rate limiting is not what everyone is thinking it is. It is not to punish non-paying users.
"Data scraping" is a big deal. This is where automated systems load the website or app and pull your tweets/data. It's a huge security issue. Automated systems are pulling every tweet/word/user account information to store in an unknown database somewhere else.
This could be state actors like China, the US Government, Australia, or other bad political actors like PAC's that are trying to gain access to everyone's information to analyze and use for nefarious things. Manipulating what is said on the site can be done at scale with data scrapping.
It could also be used to figure out the identity of Anons or to punish people in their country for what they tweet. Looking at you #Australia and #Canada and #UnitedKingdom
The temporary measures of limiting tweets is to protect users just as much as it is to protect the entire Twitter network from going down. They are currently scrambling to get ahead of this and tune their network security to block it from happening again.
It's also important to note that twitter has 500,000+ servers. That's not free. In cloud data centers, the companies that use them have to pay for what is called "ingress and egress" of data going "in and out" of the servers. A data scrapping event that is large enough for them to start limiting means that it was a MASSIVE event that could be considered an attack on the site. It would also put massive load on their servers and cost them so much money it could threaten the site's financial ability to keep running. It could be on purpose to put twitter out of business from cost alone.
Many people are misunderstanding why @elonmusk wants people to pay for twitter or for the twitter API (a programming interface that can pull data for other sites and apps).
The reason he wants people to pay is because if China or porn companies want to create massive bot farms of fake accounts, it is currently free. These bad actors are highly skilled and operate like a business. They have professional staff that continuously change their tactics and Twitter engineers have to fight 24/7 to stay ahead of them. If they have to pay for every account or pay to use the API, it would cost them A LOT of money. This limits the amount of people who could create bots, put automated porn on here, and the hacking/scrapping/DDOS attacks on the site. It protects you.
It also guarantees twitter will continue to exist without bloating it with tons of ads. This is all a part of the plan to create a free-speech place we can enjoy without being controlled by outside actors or advertising companies. I know $8 is a lot to some people but, it is for many reasons. None of the reasons are to hurt or punish people.
#TwitterDown #TwitterLimits #SolutionsArchitect #CloudSecurity #FreeSpeech
R. Jason Kerney retweeted
Your team can learn prioritization, thin-slicing, evolutionary design, TDD... the whole shebang.
These are just skills. You don't have to be born to them.
R. Jason Kerney retweeted
The point of TDD is not "high test coverage."
It might be a side-effect, but it is not the purpose.
R. Jason Kerney retweeted
Replying to @tottinge @tom_a_r_johnson
Since it is IN git, then git analytics should also work with teams, and maybe even pressure Jira etc to recognize co-creation.
R. Jason Kerney retweeted
Git docs recommend microcommits!
"As a general rule, you should try to split your changes into small logical steps and commit each of them. They should be consistent, working independently of any later commits, pass the test suite, etc. This makes the review process much easier"
Hello #Dotnet peeps. I wrote tools to help you with version info.
github.com/jason-kerney/what…
Allows you to have your version easily from within your app.
github.com/jason-kerney/DotN…
Allows for command-line management of your applications version (similar to "npm version" command)
I talk about gaining permission from employees before making changes. This is an often overlooked step in change management. - mailchi.mp/d642c1193669/new-…
Oh Friday, April 7th, my first blog in a year will be publishing. It is on the power of consent in change management to gain engagement.
The permission from the employee is something often overlooked, but truly powerful.
R. Jason Kerney retweeted
If you release a couple times a day so that the deltas are small, have a no-known-bugs-on-release policy, have plenty of tests, most automated, work in an ensemble so the code is reviewed by multiple eyes as it's written, there's essentially zero risk to a Friday release.
R. Jason Kerney retweeted
When I talk about releasing on Friday, many ppl respond with "why not wait 'till Monday." That's missing the point, which is that your code should be high enough quality that you feel confident releasing whenever it's convenient, even on Friday (and no, that's not a "fantasy").









