BrianGetsBinary

Angular 12 and SSL is much easier than you think. Want to know how it's done? Check it out right here - briangetsbinary.com/angular/softwa…

@HedgeyeComm @TikTokInvestors Computer is massively constrained so this makes total sense for both companies. Of course this is good news from an IPO perspective but I don’t understand why anyone can be so negative about it.

lol unreal… not sure w will ever see anything like it again in our lifetime. The coordinated effort is stunning.

@AntonMartyniuk Automapper is a cancer in most code bases and now it’s a disease you pay for

𝗧𝗼𝗽 𝟭𝟬 𝗺𝗼𝘀𝘁 𝗵𝗮𝗿𝗺𝗳𝘂𝗹 𝗡𝘂𝗚𝗲𝘁 𝗽𝗮𝗰𝗸𝗮𝗴𝗲𝘀 𝘆𝗼𝘂'𝗿𝗲 𝘂𝘀𝗶𝗻𝗴 𝘄𝗶𝘁𝗵𝗼𝘂𝘁 𝗿𝗲𝗮𝗹𝗶𝘇𝗶𝗻𝗴 𝗶𝘁! You might think these popular .NET packages make your life easier — but they often introduce hidden issues 👇 1️⃣ 𝗔𝘂𝘁𝗼𝗠𝗮𝗽𝗽𝗲𝗿 Encourages overly-complex mapping logic hidden behind profiles. AutoMapper is slow and makes debugging almost impossible. 👉 Better choice: Manual mapping 2️⃣ 𝗠𝗲𝗱𝗶𝗮𝘁𝗥 Adds unnecessary reflection overhead and complexity. 👉 Better choice: Own manual handlers 3️⃣ 𝗡𝗲𝘄𝘁𝗼𝗻𝘀𝗼𝗳𝘁.𝗝𝘀𝗼𝗻 Heavy and slower compared to newer, built-in options. 👉 Better choice: System.Text.Json

@SilveradoLegion @valigo I do it all the time. I’ll build on windows, write scripts in powershell and it just works on Linux. The portability is great. I still use shell scripts too but overall the tool optionality is fantastic.

@valigo I can tell you that there is one person using Terminal who isn’t a Linux person

This is so funny - Microsoft had their own tools with the same functionality since forever. But the only people using terminal on Windows are Linux users, so it's easier for Microsoft to port coreutils than to teach Linux people PowerShell

@LyalinDotCom Very cool and nice work!

I always wanted to build a mini game that was the popular "AC-130 gunship hovering over some sort of mission in progress providing covering fire" I tried many times and failed, but last night I think I nailed it Very basic gameplay for now: death-from-above-3199e.web.app

@m2jr GitHub project that’s installable via a npx?

Has anyone created an internal GitHub but for skills and prompts (not code) that can be hosted internally to a company and have non technical contributors?

@johnarnold We do know how this will play out and we won’t need UBI, insurance or more taxing - we can look to the Industrial Revolution and understand what market dynamics and societal changes will synthesize. AI will be an Industrial Revolution more than most realize

A host of policy responses have been proposed: UBI, wage insurance, taxing AI, workforce retraining, shorter workweeks, expanded social insurance, giving people equity in AI or broader stock market. But it’s hard to know what to do when we don’t know how this plays out. 20/n

After many conversations over past year with friends, business associates & policymakers about the future of AI job disruption, I’ve tried to get my thoughts in order. With the caveat that I have no specific AI expertise, here they are. Comments and corrections encouraged.🧵 1/n

@_yiyuan_ @johnarnold This is fundamentally not true - the release of Claude Opus 4.5 will go down in history as a seminal moment in computing. We gained a new superpower and can now do things previously unimaginable.

@johnarnold I don’t think it’s the model that crossed a certain threshold. The adoption has been driven by the “killer app” — Claude Code, which increased token usage exponentially. Whether this would happen elsewhere, and is sustainable, to me is questionable.

The fallacy of this is that more creates more. More hours, more hiring, more something. And it is true in a sense. If you put in more work, more work will happen. But I think for most startups, the leverage is really in how differently you approach the problem, how well you cultivate your team, and the strategy. Any large company can outspend you on hours. They have thousands or tens of thousands more people, spending more hours. If hours worked were the metric, every large company and government organization would always win and do the best work. More hours, better output. This thinking is often representative of younger founders, where the startup becomes their identity and life. They have a hard time doing anything else, and cannot understand that your work is not the person that is you. But activities outside of work can grow you as a person too and make you do better work. I’ve never worked this way. As a designer, I always saw the need to take a step back, to take a break. At times, I might work 12 hours or 16 hours, or whatever amount was needed, but it wasn’t the norm. You just can't grind design, you need inspiration. But taking that step away from the work, would give me more perspective, inspiration and I could approach the problem differently or I could just see the solution. Grinding is never good for any creative problem, and startups or creating new products are often mostly about creative problem solving. Grinding works ok for email jobs, or where you just executing on very clear playbook. With Linear, we’ve never worked this way. We work reasonable hours, 5 days a week. All of us founders have families. Many of our employees have families. I personally stop every evening, spend time with the family, cook dinner for the family, eat dinner together, and focus on things outside of work. Sometimes I work in the late evenings or weekends, but to me the pride is that I don’t need to. Company should be succesful without it. My goal is to build a company that is sustainable in the long term, and doesn’t require heroics or personal sacrifices every single day. There are times when our team is heroic. Launches, incidents, some other work that just needs to be done. They will work late into the night because they know it is the right thing. But we don’t require that every day or every week, and the more this happens, the more I think it is a failure of our company and leadership. The team and the leaders should always keep a reserve to use when something is needed. Our thinking was also that quality, which we value, doesn’t emerge from working more or stressing people more. It emerges when you create the conditions for it to emerge. Often it is the appreciation, space, time, and how the person feels. A person who is rested will do better work. I wouldn’t attribute much of our success to working a lot. The success came from having clear thinking, ideas, and focus to do the right things. I sometimes wish we could move the culture more toward a Zen master. Real mastery is not exerting the most effort. It is achieving the outcome with the least necessary effort.

@elonmusk @lxztlr @JeffBezos @zerohedge

@JeffBezos @zerohedge Ad astra per aspera

All personnel are accounted for and safe. It’s too early to know the root cause but we’re already working to find it. Very rough day, but we’ll rebuild whatever needs rebuilding and get back to flying. It’s worth it.

@raimeyuu @Aaronontheweb To that end, I think the architecture of these agents and agentic experiences is fascinating and only want to spend more time understanding them. Juniors have to have that curiosity and not just get stuck on Vibe Code Island

@raimeyuu @Aaronontheweb Foundational skills are more important than they have ever been and will be more valuable in the future. I think the senior engineers are self selecting into AI because it’s incredibly exciting. The junior looking to upskill is stuck because he just had an off to the AI

Do software development meetups and conferences talk about software any more?

@xoofx Nice work. Been waiting for something like this. Will definitely try it out

I'm thrilled to release CodeAlta - one of the first efficient AI coding-agent TUIs built entirely in C#/.NET 🚀 I've been developing and using it daily for the past 3 months, and I hope you enjoy it as much as I do! 🤗 Retweets are highly appreciated! 🙏 CodeAlta brings you a beautiful, colorful timeline interface, multiple threads in the same workspace, a real prompt editor experience, quick file viewing/editing with syntax highlighting, in-app model provider configuration, a multi-agent-ready environment, and much more! ✨

@KarenPayneMVP Copilot is pretty much unusable in VS2026. I’ve gone full time VS Code because due to those product failures. I only use Big Boy Visual Studio if I must

VS2026 is the most frustrating version of Visual Studio I have ever used. Top of my list: - Installation issues - Missing dropdowns for quick actions - Constant Copilot issues - Failures for Copilot while debugging And today, two attempts, restart, one attempt. And note that VS2022 generated a message for the same project with no problem (using net9).

🚨Breaking: Patrick Dorgu wins Manchester United goal of the season and will win premier league goal season too

@kristijan_kralj Don’t take my IRepositoryService away! How else am I going to query the database!

The hidden cost of "enterprise" .NET architecture: Debugging hell. I've spent 13+ years in .NET codebases, and I keep seeing the same pattern: Teams add layers upon layers, to solve the problems they don't have. IUserService calls IUserRepository. IUserRepository wraps IUserDataAccess. IUserDataAccess calls IUserQueryBuilder. IUserQueryBuilder finally hits the database. I've seen a lot of classes having one-line methods whose sole purpose was to call the next layer and that's it. But to change one validation rule, you step through 5 layers. To fix a bug, you open 7 files. The justification is always the same: "What if we need to swap out Entity Framework?" "What if we switch databases?" "What if we need multiple implementations?" What if this, what if that. The reality: Those "what ifs" don't come to life in 99% of cases. I haven't worked on a project where we had to swap the ORM. But I've seen dozens of developers waste hours navigating through abstraction mazes. This happens with both new and experienced developers. New developers asking on Slack all the time: "Where to put this new piece of code?" But senior developers are too busy to answer that message. Why? Because they are debugging through the code that has more layers than a wedding cake. The end result? You spend more time navigating than building. Good abstractions hide complexity. Bad abstractions ARE the complexity. And most enterprise .NET apps? Way too much of the second kind.

The advent of agents causes you to think much broader and bigger in scope of features and deliverables. Classical workflows are not going away but the real alpha is in how you can design those with latent tools and agentic applications

Where were you at the on April 27th, the day of the great token pricing reset?

@awakecoding For deep dive problems and things that I need its advanced tooling for, I use it. Beyond that I avoid it because vs code is so much faster and has better AI tooling. Still a fan but VS code is becoming my daily driver

The biggest surprise is to learn that a lot of Visual Studio users don't even use its debugger very much or at all. Why? 🤔 It's like one of its best features

Azure Functions + OTEL = the red headed stepchild of the .NET ecosystem

@tomasz_ducin @gregyoung I will die on this hill with you. If you don’t know the proper guard rails or aren’t capable of understanding critical components and know when to course correct you won’t vibe code for long. People with strong fundamentals will be more valuable than ever

That's why proper architecture will value more than ever: - modularization by usecases and/or roles, not by data - integration patterns and strictly defined contracts - removability and replacability in favor of long-term code maintenance (@gregyoung's art of destroying software)