Brian Kelly

Be sure to mark your calendars for this one! #kcdnug #dotnet #questanalytics

3

Financial scams are becoming more advanced and believable. It is important that you vet every source of information, question every link, and double-check senders of correspondence. If you take just a few seconds more to look into an email or text message, you could be saving yourself thousands of dollars. Banks take #cybersecurity very seriously and often provide quick and easy ways to check whether or not they sent a message to you or not. Understanding and preventing financial scams starts with education. Talk to your friends and family about how to stay safe online. #Fraud #MastercardEmployee

27

James Grenning course is top notch - well explained, easy to follow, and appropriately deep.

5

(2)Yes, the numbers are crazy. Amazon CEO Jassy: "...saved 4500 of developers-years of work for approximately $260M of annualized efficiency gains...'. Indeed these numbers are crazy but they shouldn't be. Organizations that are not already deep into applying AI to various stages of the software development chain are destined to lose. And I mean DEEP application of AI rather than various shades of AI washing. Requirements generation and tracking, code and test generation, AI driven CI/CD automation (review, test, and staging, team communications, etc). And of course application of organizational RAG everywhere possible (read backend persistent data). If teams are still waxing philosophically on the merits of OOP vs functional, declarative vs imperative, documentation, styles and linting, etc, they are wasting their time and that of the organization. These matter to us. They do not matter to the machine.

1

BDD vs. Traditional Frameworks: A Comedy 😂 Act 1: The Skeptics: "BDD? Gherkin? More work for no reason! I'd rather wrestle a kraken than write in plain English!" Act 2: The BDD Evangelist: "Hold on, my friends! BDD is like a well-organized toolbox, not a kraken's lair. Let me show you the light!" Act 3: Separation Anxiety (Solved): "With BDD, test cases and code are like a happily divorced couple – living separate lives but still getting the job done. No more Frankenstein test methods!" Act 4: Reusability Rhapsody: "Steps are like LEGOs – build once, use everywhere! Traditional frameworks? More like a jigsaw puzzle with missing pieces." Act 5: Hooks – The Heroes of the Hour: "Logging, cleanup? BDD's hooks swoop in like ninjas and handle it all behind the scenes. No more code clutter!" Act 6: Onboarding Nirvana: "Newbies, rejoice! BDD specs are your onboarding manual. Learn the features, copy the steps, become a testing superstar in no time!"

5

1 Comment

Functional Requirements Get You in the Door, Non-Functional Requirements Keep You There. 👈 When we talk about software development, it’s easy to get caught up in delivering the features that users demand. Functional requirements like login systems, data entry forms, and reporting tools often take center stage. But here’s the thing: while these features might get you in the door, they aren’t what keep users coming back. Non-functional requirements—like performance, security, scalability, and reliability—are the unsung heroes that determine whether your software can stand the test of time. 🟢 Security: Keeps your users’ data safe and builds trust. 🟢 Performance: Ensures a smooth, responsive experience even under load. 🟢 Scalability: Allows your system to grow alongside your business needs. 🟢 Reliability: Guarantees uptime and availability when users need it most. It’s not enough to just deliver features. You need to deliver quality, and that means giving equal weight to both functional and non-functional requirements. Don’t just meet expectations—exceed them by building software that not only works but works well under all conditions. #SoftwareDevelopment #QualityAssurance #TechLeadership #webdevelopment #NonFunctionalRequirements #SoftwareEngineering

1

Not sure why the Vue community was and (pretty much) is, scared of the composition API. I was too, to be honest. But I have loved it for the past few weeks as I use it more and more. If you are still hanging in limbo, there is a great series on Laracasts by the great Jeffery Way, himself. There are also a couple of free courses on Vue School for Vue3 composition API. You should be up and running in 2-3 days if you have used Vue 2 in the past. #vue #vue3 #compositionapi

25

8 Comments

One of the teams I manage came up with some code review principles in a workshop I ran recently. How do your teams think about code review? What's worked well or caused issues in the past? Every team is unique so I'm curious how others have approached this 😃 --- Authors should: - stop starting, start finishing - keep PRs small - provide evidence - move the PR forward Reviewers should: - provide an outcome within 24 hours - debate productively (https://lnkd.in/exVeR-cy) - clearly indicate nits - don't be afraid to jump on a call https://lnkd.in/eEdfRuU2 #codeReview

27

5 Comments

Many non-technical people involved in product development and close to the technical teams are unaware that all developers are not created equal. In addition to the obvious skills differences that occur there are different developer archetypes. You need to ensure when creating a team that you have the right mix of archetypes for the team to be successful. It’s yet another challenge when creating high-performance teams. Some companies, such as Facebook, do this formally. Many companies do it informally, and then some don’t do it at all (much to their detriment).

9

Don't wait too long to consider QA for your projects, playing catch up is never fun or financially practical. If you're looking to build your team or need to ramp up to finish a project, let us handle this for you. Fractional resource options available for tight budgets or needed versatility. #QualityAssurance #QA #ProjectManagement #ResourceManagement #FractionalResource #BudgetFriendly #Versatility

3

1 Comment

How to Sabotage Sprint Planning (episode #4) Ignore Technical Debt! OtterWorks Website: https://buff.ly/4hZMiJS Development Deep Drive: https://buff.ly/48ZTscK

3

A great take on the topic of Legacy Code / Legacy Systems. Some of the concepts mentioned in the article may rub people the wrong way, but when you read the details it makes perfect sense. There is some solid advice in here. "People call some code legacy when they are not happy with it. Usually it simply means they did not write it, so they don’t understand it and don’t feel safe changing it. Sometimes it also means the code has low quality1 or uses obsolete technologies. Interestingly, in most cases the legacy label is about the people who assign it, not the code it labels. " https://lnkd.in/gAhihr9i #softwareengineering #dev #coding #softwaredevelopment #programming

3

How does cloud-based device testing stack up against maintaining in-house device farms? How does one begin to navigate choosing a mobile testing approach? Modernizing your testing process in today’s challenging landscape – where to begin? These are a few of the many questions Marcus Merrell and I will address in part one of a two-part webinar series on a few things you need to get started with cloud-based device testing on May 21. We can’t wait to see you there! https://lnkd.in/dJuwZqNX

19

Whether you're on a cattle farm or in IT, you must keep an eye on your investments at all times. No one knows this better than [[Tag: Brett Dawson]] from Fidelity Investments! In this new Main Scoop, Brett joins [[TAG: Greg Lotko]] and [TAG: Daniel Newman]] to talk all things observability, and how it fits in with #AI and #hybridIT strategies. https://dy.si/Z5jWB3

31

1 Comment

Corporate IT has no place on the path to production. I see LOTS of portcos that hold onto shortcuts they took when they were small. Corp IT runs Jira, or email goes out through the corporate mail gateway. Call it technical debt if you like, and taking on technical debt makes sense when you're a startup. But when you've made it past that stage, it's time to pay it down. Corporate IT is incredibly valuable. I was the Director of IT before I decided to dedicate my career to production web operations. I knew my CDW rep very well. Corporate IT can handle: corporate email, Salesforce, Tableau, calendaring, Zoom, Dropbox, etc. Corporate IT cannot handle: production SMTP gateways, Jira, Confluence, GitLab, Launch Darkly, Datadog, Cloudbees, etc. I don't care in the slightest which actual vendors you use for these functions. I've seen corporate IT change SCMs to "save money" without any input from engineering and set the entire organization release schedules back by more than 8 months because it turns out that GitHub "runners" have security concerns. People have made changes to corporate email and suddenly customers no longer receive notifications, and no one in engineering knows why. Engineering (including Operations) is where the money is made in a software company, and they need to own the path to production. Think of it in terms of "chain of custody" considering the concern over supply chain attacks. In the chain of custody, we don't just let someone with completely different concerns handle evidence. Why would you? #devops #sre #engineering

63

11 Comments

My initial involvement with .NET was in 2008. I started with WinForms, then UWP, and most recently Blazor, with some Web API work as well. I also did/do some Xamarin.Forms and .NET MAUI on the side. I've worked with SQL Server, Oracle, and SQLite. The last year has broken me. Without work and income for at least a year I've been forced to start tapping retirement funds at least a decade before I had planned. (In fact, I had always hoped to take my last breath at the keyboard trying something new.) The constant fruitless efforts in the job search, including massive numbers of ghosting events; postings I've applied for, never had a response, but continue to be posted; the horribly vague pieces of textual trash called job descriptions; and so on, have made me give up. I just can't do it any more. Without the generosity of friends, right now I'd either be dead, in jail, or living under a bridge. This was not the way I saw my future. I dedicated my career to .NET and I ended up broke and homeless, in massive amounts of debt that can't ever be repaid. So I'm backing away from full-time search. That said, I'm still looking to keep involved with the .NET technologies but in a part-time manner, as well as build upon the meager retirement income. I'm looking for a Blazor or MAUI project to work on, perhaps a lower-priority solo developer effort, demo, or POC requiring around 20 hours a week. If there's some other .NET technology, give me a little time and I'll get up to speed. No charge until I start doing your work! It probably could go unsaid, but I'm not interested in being contacted by recruiters. You're the ones that did this to me with your gross incompetence and terrible work practices. Yes, I'm bitter, and I hope every one of you that ever ghosted me suffers like I am.

2

5 Comments