Matt McLaurin

No matter what language you’re programming in, errors happen. One great thing about #Rust is that you can diagnose and act on them quickly – if you know which tools and mechanisms to use. Learn more on our Tech Blog. https://bit.ly/4gmccX5

2

The latest Qwen2.5 Coder models outperform Sonnet and 4o on some benchmarks. Try it on Wingman today!

4

I wonder. Why when you cut a class from one source file to paste in in another - you have to deal with all the imports once again. It is really annoying. Ok, ok, you can move a class by F6/Refactoring. But Cut-n-Paste experience is way more natural than picking a target package/whatever destination you fancy to move your stuff to. Q. Do you experience the same frustration of this micro-UX problem?

1

6 Comments

[Reiterating] I never understood income tax deduction from a salary, to begin with. I mean, how can they tax an income which never came in, or say, which an employee never received, or in other words, which never actualised? It’s like, punishing someone for doing something, that the one never did, but was about to do. Like, penalising someone for having something extra, that the one never had but about to have. All that, merely, on the basis of potentiality. Statistically speaking, that potentiality has never been actualised in the past; and, eventually, never will — provided this system remains deplorable as such. Moreover, they deduct a hefty amount every month — and that’s preposterous and outrageous.

23

If you’ve got the start of a prompt, Copilot will offer to auto-complete it to get to a better result, suggesting something more detailed to help ensure you get what you’re looking for. That not only speeds things up, it offers you new ideas for how to leverage Copilot’s power. https://lnkd.in/gqKgkGBk

3

Not my job should never be in your vocabulary. My job is to serve the business to meet our objectives. Make a case for things that will give big improvements, make trade offs. One of the keys to a good teammate and bringing value to the business.

3

2 interesting topics from proposed regs I had not read before - I'll link the 180 page document in the comments. First - level-funded plans coming under scrutiny. I think the most fun language in here is the consumer protection worries coming from "interested parties..." I consider that whole section dystopian level tone-deaf. Something like: "Allowing small employers to create a better risk pool is a risk to all of us because it destabilizes our vital small group marketplace." Oh really? Tell us again how that small group marketplace is so viable and helpful currently. Second - fixed medical indemnity plans possibly no longer to receive tax advantage at all. Aflac won't be happy if that pans out.

6

1 Comment

Fascinating to see Amazon leveraging GenAI to transform software development lifecycles. As someone who's discussed the potential of GenAI with clients, this real-world application by AWS, drastically reducing upgrade times and enhancing security, is a game-changer. Excited to see how this will continue to reshape the SDLC landscape!

16

Watched a portion of the old Brian Will video on why OOP is bad (https://lnkd.in/epvfRpPR), and bombed out fairly hard when he came out with the puzzling assertion that messages between objects properly speaking shouldn't include object references. Well, there goes your visitor pattern; there goes the UI staple of registering objects with some event bus for callbacks when particular events happen. Is there some source in the literature (Alan Kay, I guess) for this odd restriction? It seems like a basic misapprehension: sure, messages should transfer representations of internal state and not haphazardly leak references to the state itself (otherwise external parties can mutate it without going through the owning object's protocol), but it's also a pretty basic affordance of message-passing systems that the addresses of things that can receive messages are first-class things that can be passed around (compare URIs in REST, or channels in pi calculus). The other odd assertion was that permitting many objects in an arbitrary graph to hold a reference to an object and access its methods was as bad as having global shared state. It fairly obviously isn't: the ability to exercise the protocol for reading or updating a particular bit of state can get passed around to wherever it needs to be, but isn't immediately available to everything, and pretty much the whole point is that you're passing a pointer to the protocol, not the rights to inspect and modify the data structures it guards. It seems that Will wants to argue for a hierarchical flow of messages down a DAG-shaped stack of routines and subroutines with a single controlling root procedure, rather than a potentially cyclic call graph with objects fielding requests from all angles. In practice that's what your average Spring Boot service actually does of course: controller to service to persistence or external client layer, and back up again. But (and this is an argument for a future post) that's because the average Spring Boot service is fundamentally procedural code, with a bit of indirection between modules. Other topologies are possible, and appropriate for particular use cases. The most generous reading I can give of Will's argument is that OOP offers more flexibility than perhaps a majority of actually existing programs really need, and we'd be happier and less burdened by object bureaucracy if we wrote those programs in a more constrained idiom. I actually think that's kind of true, but haven't got to the bottom of what it means in practice just yet.

2

‘In this episode of “The Engineering Room” Dave Farley chats with renowned author, speaker and expert software developer Kevlin Henney.’ https://lnkd.in/gsenvBMQ ‘In their wide-ranging discussion they talk about: • Why Kevlin Henney is famous for big public software failures! • Software Engineering, mathematics and the interesting gap between formal programming and sloppy humans. • Architecture, empiricism and three ideas for design. • Coping with incomplete knowledge and making stuff that works in the real world. • Confidence, certainty and loose-coupling. • Learning from actual failure, not just simulation. • Programming is deceptively easy to start, and gets complicated really quickly: Low Code is no exception.’ Continuous Delivery Ltd Bernard McCarty #ContinuousDelivery

21

It is CRAZY how much weaker OpenAI GPT-4o is at coding from the completions API than GPT-4. I'm not sure if this is the intended result, but very surprising nonetheless. The training recency is very evident, i.e. it knows about much more modern things, but the difference between its logical output is great with GPT-4 just thinking in a much more sophisticated fashion.

5

1 Comment

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

3

Recently I was reading about the VW data disclosure, and I was thinking: could an LLM spot this? So I built a small prototype using PDL script, and the results are pretty good to be honest! More detailed information here: https://lnkd.in/dqJSMPkU

5

Capital One's journey to serverless architecture has taught our teams many valuable time-saving lessons. Two of our tech leaders, Lina and Fatma, are sharing their experience and a few tips for success. Check out what they have to say and learn more about how we’re building with serverless at scale: i.capitalone.com/GCRAl5D9G

2

Today, the SAS9 division embraced creativity and innovation with a twist on a beloved tradition: non-traditional gingerbread house building! The tradition of decorating gingerbread houses started several hundred years ago — a reminder of how long-standing practices can bring joy and connection. Just because something has been done the same way for years doesn’t mean it has to stay that way. Our activity was a fun and delicious way to remind ourselves of the power of thinking outside the box. By challenging traditional methods, we unlock new possibilities, whether in holiday fun or tackling workplace challenges. How are you reimagining traditions or approaches in your work or personal life? Share your ideas below—I’d love to hear! #Innovation #TeamBuilding #HolidayTraditions #Creativity

22

6 Comments

Different developers and different companies have various techniques for combatting distractions. What tools do you use to keep interruptions and diversions at bay?

3

I once asked a lead engineer on Angular: Which is better: Angular or React? His response: "Both require good engineering to be effective." So, my developer friends, consider this a reminder that "frameworks" like Diátaxis are fine, but they still require good engineering--such as UX, information architecture, style, maintenance processes, and so on--to create great documentation experiences for your customers. Alas, the framework alone isn't enough.

36

7 Comments