# Visual Basic Visual Basic is an object-oriented programming language developed by Microsoft for creating type-safe .NET applications. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## No robots in the gym, with Keith Hoodlet DevFeed: [No robots in the gym, with Keith Hoodlet]() Original publisher: [Read original article]() Author: info@1password.com (Dave Lewis) Published: 2026-08-14T00:00:00Z Content type: article Language: en Sources: [Blog on 1Password Blog]() Topics: [Security](), [Artificial Intelligence](), [Computer science](), [Visual Basic](), [GitHub]() Tags: [ai](), [blog](), [career](), [github](), [leadership](), [podcast](), [podcasts](), [research](), [security](), [spoof]() ### AI overview An article about Keith Hoodlet's nonlinear path into security research, his work at 1Password and Off-by-1 Labs, and lessons from his experience in psychology, computer science, leadership, and AI bias research. ### Source excerpt Listen to the episode on Apple Podcasts null Listen now Listen to this episode on Spotify null Listen now This week on the Chasing Entropy Podcast, host Dave Lewis sits down with Keith Hoodlet, Director of Security Research at 1Password and leader of the newly formed Off-by-1 Labs. Keith's mission? "To throw stones at glass houses, not to hear the crash necessarily, but to help people build better and more secure houses." A villain-turned-hero origin story As Keith puts it, "I've always been really focused on skill acquisition over formal titling or formalized skillsets in many ways." After all, he got his start as a self-proclaimed "unpaid punk on the internet, messing with video games, mostly." As a teen, Keith would spoof other Diablo players by using a trial key from the back of a CD case, and taught himself Visual Basic so he could spam StarCraft opponents. He realized early on that he was "pretty good at the whole computer thing." That's why he decided to major in psychology - it was something he couldn't do. He wanted to understand people better. Graduating in the midst of the housing market crash had him working odd jobs for several years. He returned to school for computer science, only to drop out when he received a job offer. From there, he built his career gradually through roles at Bugcrowd, Thermo Fisher Scientific, GitHub, Trail of Bits, and now 1Password. It may have been a nonlinear career path, but there have been plenty of highlights throughout that journey, including winning the U.S. Department of Defense's 2024 bias bounty program; it was one of the first times an organization paid external researchers to prove an AI system was biased and unfit for its intended use. Keith continues to make use of the varied skills he built over those years. For instance, his psychology background may not show up in threat models, but it shows up daily in his leadership: "I start from a place of approaching the other party that I'm interacting with as first a hum ## 7 Reasons Why CEOs Should Modernize their Software DevFeed: [7 Reasons Why CEOs Should Modernize their Software]() Original publisher: [Read original article]() Author: Aisling Foley Published: 2026-02-18T07:23:00Z Content type: opinion Language: en Sources: [Federico Tomassetti]() Topics: [Software](), [cobol](), [Visual Basic](), [SAS]() Tags: [cobol](), [financial-services](), [growth](), [integration](), [leadership](), [legacy](), [legacy-modernization](), [manufacturing](), [security](), [software]() ### AI overview This commentary argues that CEOs should modernize legacy software because systems that remain stable can still create strategic, regulatory, security, integration, and knowledge-retention risks. It discusses legacy systems used in manufacturing and financial services, including COBOL, RPG, Visual Basic 6, and SAS. ### Source excerpt Key Takeaways Legacy software is tolerated because, let's face it, it works, and works well. But that's no longer good enough. Nowadays, it limits an organisation's strategic options. Legacy software can slow down, or make strategic plans more expensive or complicated than they need to be. Whilst legacy software is considered stable, the real risk [...] The post 7 Reasons Why CEOs Should Modernize their Software appeared first on Federico Tomassetti. ## Visual Basic, Mentoring, and Community Building. The Artisan of the Day Is Ibrahim Abotaleb. DevFeed: [Visual Basic, Mentoring, and Community Building. The Artisan of the Day Is Ibrahim Abotaleb.]() Original publisher: [Read original article]() Author: Ana Tavares Published: 2025-09-10T15:02:15Z Content type: article Language: en Sources: [Laravel Blog]() Topics: [Laravel](), [Livewire](), [Back end](), [PHP](), [Visual Basic](), [C#](), [React](), [Vue.js](), [Front end](), [Amazon Web Services](), [CodeIgniter](), [Open Source]() Tags: [aws](), [backend](), [c-sharp](), [community](), [frontend](), [laravel](), [open-source](), [php](), [react](), [scalability](), [security](), [vue]() ### AI overview Ibrahim Abotaleb describes his journey from Visual Basic and C# to PHP and Laravel, where he has spent more than a decade building production applications. He discusses using Laravel with React or Vue on AWS, delivering systems that emphasize performance, security, scalability, and compliance, and sharing these lessons through Arabic-language teaching, articles, videos, and mentoring. ### Source excerpt Ibrahim Abotaleb shares his journey from early days in Visual Basic to a decade of building with Laravel, and how he's giving back to the Arabic Laravel community through teaching and mentoring. ## .NET Support on Heroku DevFeed: [.NET Support on Heroku]() Original publisher: [Read original article]() Author: Rune Soerensen Published: 2024-12-03T00:00:00Z Content type: release Language: en Sources: [Heroku]() Topics: [Heroku](), [.NET](), [ASP.NET Core](), [Blazor](), [C#](), [F#](), [Visual Basic](), [cross-platform](), [Open Source](), [Databases]() Tags: [announce](), [apis](), [app](), [asp-net](), [asp-net-core](), [blazor](), [buildpacks](), [c-sharp](), [can](), [community](), [core](), [cross-platform](), [deploy](), [developers](), [f-sharp](), [heroku](), [high-performance](), [languages](), [maintainability](), [net](), [news](), [nextgen](), [platform]() ### AI overview Heroku announces that official .NET support is entering public beta. Developers can build and deploy C#, F#, and Visual Basic applications using frameworks including ASP.NET Core and Blazor. The support includes a buildpack, documentation, testing, and guidance for deploying applications, including Blazor apps with Heroku Postgres. ### Source excerpt We're excited to announce that official support for .NET on Heroku is entering public beta starting today. Developers can now build and deploy applications in C#, F#, and Visual Basic, using frameworks like ASP.NET Core and Blazor, all with the simplicity and flexibility of the Heroku platform. .NET has long been one of the most [...] The post .NET Support on Heroku appeared first on Heroku. ## Microsoft's changing platform support and the challenges for managed developers DevFeed: [Microsoft's changing platform support and the challenges for managed developers]() Original publisher: [Read original article]() Published: 2013-05-12T00:00:00Z Content type: opinion Language: en Sources: [Front Page on ReactOS Website]() Topics: [Microsoft](), [deprecated](), [Maintainability](), [Visual Basic]() Tags: [deprecated](), [developers](), [free](), [maintainability](), [microsoft](), [open-source](), [os](), [react](), [reactos](), [win32](), [winapi]() ### AI overview The article discusses how Microsoft's platform changes and deprecations affected managed developers. It considers the continued operation of Silverlight applications, the persistence of Visual Basic 6 and MFC applications, and the long-term maintainability problems created by outdated systems and limited tooling updates. ### Source excerpt In my last post, I talked a bit about how Microsoft's fixation on Metro/Modern and the appstore had resulted in it basically ignoring large swathes of its developer community. So that post got a lot more attention than I was expecting, with some agreeing and others disagreeing. Some discussions however took a turn where people began debating how much trouble, if any, developers were in with Microsoft's move. This was something that I had decided not to explore further because the previous post had already reached a fairly ridiculous length.