Marc Prud'hommeaux

🏎️💨 Making of a Ridiculously Fast™ API client in R. Why my package is **~17x faster** than the community alternatives that call the **exact same API endpoints**. 👇🏽**design choices matter** ✨ https://lnkd.in/ggi_2XyQ

129

2 Comments

Not all #IBMMQ events are equal, some you'd probably like to hold onto for longer than others. Learn how #MQEV allows you to do this and choose how long to keep the events you have captured based on any criteria you need. #WorkSmartWithMQ

5

Microservices get a bad rap due to complexity and high TCO. A lot of that is because a microservice-based application works the same way as a bunch of dominoes falling. If one misses, or falls out of order, the whole workflow stops. And you have no control over the process once your microservices start ping-ponging events and RPC's back and forth. That's why #microservices are so expensive to manage. Great blog post below by Colt McNealy about how LittleHorse can solve those problems. Give it a read. https://lnkd.in/gJECBwRu

58

Another day, another new, faster #LLM. Meet Claude 3.5 Sonnet from #Anthropic. "Claude 3.5 Sonnet operates at twice the speed of Claude 3 Opus. This performance boost, combined with cost-effective pricing, makes Claude 3.5 Sonnet ideal for complex tasks such as context-sensitive customer support and orchestrating multi-step workflows." https://lnkd.in/ecXUMhKE #AI #genAI #CX #AIorchestration

7

“For Graeber, bullshit jobs carry with them a moral imperative: ‘If you’re not busy all the time doing something, anything—doesn’t really matter what it is—you’re a bad person.’ But the flipside of that logic seems to be: if you actually like doing X activity, if it is valuable, meaningful, and carries intrinsic rewards for you, it is wrong for you to expect to be paid (well) for it; you should give it freely, even (especially) if by doing so you are allowing others to profit. In other words, we’ll make a living from you doing what you love (for free), but we’ll keep you in check by making sure you have to make a living doing what you hate.” — Geoff Shullenberger, a writing professor at New York University I couldn't help thinking that here, the professor is describing, how “open source software” thing works. And then, I found: “The free software industry, perversely enough, has become a paradigm in this respect... software engineering work was divided between the interesting and challenging work of developing core technologies, and the tedious labor of ‘applying duct tape’ to allow different core technologies to work together, because the designers had never bothered to think about their compatibility. ... increasingly, open source means that all the really engaging tasks are done for free.” — David Graeber, Bullshit Jobs

1

Part of the problem is legacy code. Even if we wrote perfectly testable code from here on out, we often still have to deal with legacy code. If you need help with that in LabVIEW I’ve got a bunch of effective tools and techniques. I’m working on a refactoring workshop among other things. If that sounds interesting let me know and I’ll add you to the waiting list.

3

2 Comments

The latest twist and turn in the open source. Methinks the author nailed it: single-vendor open source projects are going the way of the Dodo bird. Although there are many sides to this issue, have always felt that a single vendor open source project was really not a whole lot different from proprietary software because of the sole source reliance. https://lnkd.in/dQv8Y9fC

12

9 Comments

Big news today... FOSSA free plan just got a major upgrade! We want to make it ridiculously easy for development teams to start securing their software and drive comprehensive Open Source Compliance, Security and Quality -- for FREE. That's why we have now launched a new free forever plan -- built for complete workflows around the lifecycle of managing open source such as: - Open source security - SBOM management - License compliance - Quality / Obsolescence No vendor evals, no sales convos, no zoom meetings. Just sign up, start doing -- and come back if you need to scale. Let's get folks off the dev team's back and ship compliant, secure and high quality software with OSS. Check out the link to the full announcement in the comments.

92

9 Comments

How to knock veteran programmers down a peg. Test them on this: What if a meeting scheduled on the exact minute a leap second is added needs to be rescheduled to the next available "normal" minute? Tests that asses someones skill as a human compiler or quiz them about obscure language features are a poor way to find out whether they can actually deliver value to a company.

3

I need to get better at identifying and coining maxims that I've come to believe. Here's some for pure func prog • Parse, don’t validate • Make illegal states unrepresentable • Errors as values • Functional core, imperative shell • Smart constructor https://lnkd.in/gvJC7f9X This is half the battle at communicating your work and being legible. Without a hook or gateway for people to Reminds me of the not-yet-numerous-enough (but aspiring to be) 95 theses on @sliminality (@slim.bsky.social)'s https://slim.computer Yet, important context gets left behind when tacit knowledge is packaged as quips. "Move fast and break things" and "Perfect is the enemy of done" are for people with a certain proclivity. If you don't have the problem, the advice is not for you. Too often people want to pick apart some quip communicating tacit knowledge, and then claim it's bad advice for everyone. More helpful would be to reintroduce context (either historical or interpretive for the modern era). "This advice only applies if you're in this context."

2

How can you manage a software engineering team when you are not a software engineer yourself? What has helped me immensely over the years: First off, yes, I have an engineering team under my leadership. Of course, I am unable to do code reviews or advise functionally. So how do I do it? A list of points, with some nods to musical pieces. Beyonce, All the Single Ladies - NOT I am not alone in this endeavor. I have co-functional leads who I can ask and get advice from anytime. My work would otherwise be impossible. Vybz Kartel, I Can I used to work in functions that often resembled PO work. Plus, I have worked with engineering teams in close collaboration for over a decade now. So I understand and can steer the dynamics. Machel Montano, Endless Wuk I am capable of understanding the business side. If I know why and where we are going I can translate that to the team and beyond. Lisa, Rockstar Believe it or not - I can put together a couple of lines of code. I have worked on some smaller, private projects before. Do I code in my free time? No. But I have seen what the basic structures are and applied them. Danagog, Hakuna Matata I can listen and listen well. I can advise based on my professional and life experience. I have empathy in droves. I can understand the lived realist of a developer, a PO, a designer, an agile coach. Have you seen or experienced non-technical managers? What was that like? Would you be open to be managed by a manager who is not able to functionally feedback you?

38

7 Comments

I've been an engineer on call in both sprawling enterprise IT settings as well as narrower settings such as running Apache Pulsar and BookKeeper at scale. What I'm reading about wide events, canonical log lines and what Charity Majors is calling Observability 2.0 has me saying YES! But... Yes, wide events and canonical log lines are obviously a great user experience for the on-call engineer under pressure. I worked at Splunk for a while, I've seen what a powerful slice and dice machine over structured logs can do. But it is expensive! What I haven't seen yet is a good discussion of infrastructure costs. How this can be done without exploding costs? Have we designed observability data systems capable of storing huge amounts of structured wide events, with low latency queries and reasonable costs? I'd love to see a paper or a blog post or something that explores wide events from an infrastructure cost perspective, discussing the design space, factors such as scale, cardinality, query patterns, and all the associated trade-offs.

49

TIL: To get a RSS feed for a subreddit, simply add ".rss" to the end of the subreddit's name. For example, "/r/artificial" becomes "/r/artificial/.rss" 👉 https://lnkd.in/gwJuHNy7

2

A question to my friends, colleagues, and Linked-In associations that are full TDD developers. Folks who consider themselves proficient or have mastered TDD. 1. How long did it take you to to become very proficient (e.g. to start thinking fully test first)? 2. Did you have a mentor or some aid that helped you along the way? 3. What kept you going down the proficiency/mastery path? I'll start: 1. It took me about 3 years to make it a habit and for me to truly embrace TDD and find that it could replace "test after" development. 2. I did not have a mentor. I did not have YouTube or trainings. I had constraints about creating automated tests. I had teammates that were similarly inclined (constrained). 3. I immediately saw the value of automated tests. I struggled with test first getting in the way of me feeling productive (because I was not proficient and in the learning/gaining proficiency phase) with test first. I'd start every day test first and quickly transition to test after, because it was getting in the way of my "productivity and programming...damn it I just want to write the implementation!" At the end of the day I'd reflect and most days realize that writing tests after was so much slower. Slowly, my time spent test first increased. At some point I transitioned to pseudo coding my intended implementation (to satiate my need to "just write the damn code and not be bothered with tests"). More time passed and I realized that my pseudo code was an inaccurate crutch, I ditched that too and would start with a test. There was a period of time where I'd start with a test and get lost in implementing more than just making the test pass (cycles of sunk cost fallacy here, until I learned it's ok to delete and write it later - faster, better, stronger). There were periods of time where I'd forget to run the test first to see it red before making it green. Too many years messing around with mocking frameworks before learning better design. Struggles with testing internal implementation details instead of external behavior. A whole bunch of stuff I can't think of now and am probably blocking out. I stuck with it though and yikes, does it pay off. I can't imagine not doing TDD now. Coding w/o it is like running through a vat of molasses. So much time wasted in the debugger and writing things that my evil programmer monkey brain distracts me with that YAGNI. I'm writing and asking about this because last week I attended a conference where I talked with a fellow TDDer who'd heard me mention that it took me 3 years to become fully TDD proficient and he shared a similar story even though he was much younger than myself (I attribute my slow adoption due to lack of a mentor/coach and training aids like Pluralsite, YouTube, Jon Reid live coding sessions). I'm curious about others mileage on this. I'll add that I am currently 100% on board with TDD. I am also 100% always on the lookout for a new and better way to replace it. That's off topic though.

45

70 Comments

What, adding a new feature to my DLaB.Xrm library and documenting it? 🤯 I most be going crazy! 🙈 🙉 🙊 The "Where" extension method makes writing QueryExpressions in your C# Dataverse code cleaner, easier to read, easier to maintain, and just take less of your precious keystrokes! https://lnkd.in/eJEYv6QQ

27

Anyone I know personally and/or have trained interested in some aerospace work for the military? We have a company we're working with that needs some engineers for on-site dev work. So, this would be in-person in Ogden, Utah. Also, this is for another company, not for me. Junior Devs get hired as NH02 generally, after 3 years of experience they get hired as NH03. https://lnkd.in/gFEdts3a With a locality pay increase of 16.82%. They also have a 10% increase (on top of this) as a retention incentive at the location. This is not a guarantee forever, but has been around for 4 or 5 years, and theh doubt it will go away. https://lnkd.in/gXYchzEU They often can match the pay of a previous job, and the benefits for US Gov work are insanely good. The location of the work is on-site in Ogden, Utah. I believe you do have to be a U.S. citizen. Again, this is for those I personally know and/or have trained since I'll be getting for them. Here is an example project the group has recently worked on: https://lnkd.in/gt_KSFye

30

20 Comments

Alright, I used up a 2-week free trial of Cursor IDE. My experience is solid. I think I'll pay $20/m if I don't find anything better. The next ups in my list are: - GitHub copilot - Continue.dev - Cody from Sourcegraph - Tabnine - Zed Which is the best AI coding assistence in your opinion? 🤔 #data #coding #productivity

35

11 Comments

Will Devin AI replace developers? 😱 Maybe 🤷🏻‍♂️ To me personally, Devin is a development tool and not a replacement...YET 🌚 I am not denying that Devin can code really well if all the claims are accurate. Eventually, it may replace developers. But developers don’t code just to code. We build products ✅ We build solutions ✅ And these happen to be made of code. Can companies ditch all developers today and expect products to still get built and maintained to the same standard as an enterprise-level solution? Nope 🙅🏻‍♂️ The quality of a product refers to how well it solves user problems. And those gaps between code, user, and solution? That’s where good developers provide values 👨🏻‍💻✨

1