Samer Buna

JavaScript API gripe: Why do so many documentation pages miss basic things like theory of operation and if a parameter named "options" is passed in, a complete listing of all options including working examples is not given right then and there? Do they think I won't use this stuff? Do they think if I don't read all their source code I don't "deserve" to understand how to use it?

3

#postman extension for #vscode

6

Did you know PHP powers ~77% of all server-side websites and is ~3x faster than Python? Aaron Francis made a great video about how "PHP Doesn't Suck Anymore" and detailed all the new language features introduced in the past decade. My picks: - Traits - Generators - Anonymous classes - Decorators - Closures Are you using PHP in 2024? Are you planning to migrate to something else or is it working just fine for you? https://lnkd.in/g_gTy7_G

6

2 Comments

My latest Cypress.io blog post "Check URL Search Params Using Cypress" https://lnkd.in/eAaYaWae

23

1 Comment

I wrote a Cypress blog post: "Cypress Namespaces For Custom Commands" https://lnkd.in/gVNQkBq4

17

When working with BigInt add this code in your middleware or on top of your API route to fix serializing BigInt error. #BigInt #Javascript #API

2

Onboarding new devs used to be a pain. Now with .NET Aspire, it's a breeze! 🌬️ One command to rule them all: 'dotnet run'. How has Aspire improved your team's collaboration? https://buff.ly/47jeMJm #dotnet #aspire #onboarding #localdevelopment

1

1 Comment

🚀 Introducing Propshaft in Rails 8: A Modern Approach to Asset Management 🚀 Web applications need to quickly and efficiently serve CSS, JavaScript, and image assets. One of the most effective methods is to "fingerprint" an asset and serve it by its fingerprint with a cache header that never expires. Enter Propshaft: Propshaft digests the image at /images/foo.png and generates a URL like /images/foo-586e0b396456675e08bba21db5941a3099b07766084e51400576f7622c5217cc.png with a cache header that effectively never expires. 🎉 Why Propshaft over Sprockets? Legacy to Modern: Sprockets, introduced in 2009, predates JS-based asset pipelines like Webpack. It handled everything from compiling SCSS to minifying JavaScript. New Era: In 2024, most browsers efficiently download JS and stylesheet assets without an asset pipeline. For more complex needs, tools like esbuild can be used. Focused Efficiency: Rails now focuses on generating fingerprinted URLs for images, videos, and media files, leaving CSS and JS compilation to modern browsers or more capable asset compilers. Propshaft is all about efficiency and modern web standards, making Rails 8 even more powerful and streamlined. Stay tuned for more updates on Rails 8! 🌟 #Rails #RubyOnRails #Rails8 #WebDevelopment #TechNews #SoftwareEngineering #BackendDevelopment #OpenSource #AssetManagement #WebPerformance #TechCommunity #Programming #WebDev

5

This is an interesting usability issue with post authoring on LinkedIn. I see that the "Rewrite with AI" call-to-action doesn't become activated until I have a sufficient amount of content in my post (presumably having to do with either the underlying API constraints or the value-add of the model). But, when the feature is "OFF" and then becomes "ON" while I'm typing, I can't help but _feel_ as if the application is telling me that it detected a problem with my writing and is now _suggesting_ that I use AI to improve it. I suspect that a better experience would be to always show the "Rewrite with AI" as actionable; and then, explain that I might not have enough input text at the time I try to consume it. This way, the activation of the button cannot be confused as an inherent judgement on my writing ability. #UserExperience #ProductDesign #HumanInTheLoop

5

2 Comments

We are witnessing firsthand that the most important property of a software system isn’t how well it serves its users now, but how easily it can be adapted to serve its users better in the future. It is uncomfortable to recognize that we do not know the future. But fundamentally, we have to believe that there is always more value to unlock in the future than we could possibly provide in the present. There is of course a balance—companies have to thrive in the present so that they continue to be around to build for that future, too. But in general, this has never been more apparent than the GAI revolution. We are experiencing a moment in which every product in the industry must make a massive shift in how they work and how they think about products. But if we get it right, we unlock transformative value, not just for ourselves, but actually for humanity as a whole. It’s still important to focus on the outcomes—what happens for your users as a result of this new technology? That’s just as true for developers as it is for every other software user. The outcome we are going for is not just “deliver a feature today.” It’s “build a system that is so easy to adapt that it thrives even more in the unknown future than we can possibly imagine now.” We live in a world where the potential to enable that flexibilty is greater than it ever has been, so long as we embrace the change that AI brings, and stay focused not just on the technology, but genuinely focused on using _every_ tool at our disposal to enable a beautiful _future_ product that we cannot yet imagine.

36

7 Comments

🔒 Securing your #SpringBoot webhooks? Learn how to test a Spring Web MVC HandlerInterceptor with JUnit 5! ✅ Dive into unit tests, MockMvc, and more to ensure your endpoints are protected. Read the full guide: https://lnkd.in/emEDUGBN #SpringFramework #Java

8

Working on a specification for https://lnkd.in/g-pBfAQv. Then I can verify it with tests and https://blprnt.tech/. I'm reminded that wormwood is optimized for readable source code, not UX. There is very little syntax validation.

4

The Foreign Function & Memory API allows Java programs to call native libraries and process native data without requiring the Java Native Interface. Read more 👉 https://lttr.ai/AT1Zf #PopularProgrammingLanguage #UpcomingJavaoneConference #LatestIteration #EnhancementsDesigned #BoostProductivity #ImplicitlyDeclaredClasses #BlogPostHelpful #NativeLibraryCalls #ConcurrencyMadeEasy #ReceivedGlobalEndorsements

2

Progress = your QA release process growing from 15 minutes to 5 hours. A stat that’s both invigorating & frustrating at the same time. But I think the single best thing you can do to delight your customers is to personally guarantee “it just works”.

10

🌐🌐🌐 New JavaScript Set methods🌐🌐🌐 Finding the intersection, union, and difference between sets, among other set-related tasks, is now a piece of cake. Available in Node 22+, Chrome/Edge 122+, Firefox 127+, Safari 17+ Link: https://lnkd.in/gKUe_ycu

6

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

React v19 beta version is released and there are some exciting changes and features that supports full stack architecture!! https://lnkd.in/gTDekJsz https://lnkd.in/ghQ2m-dd #reactjs #javascript #frontendprogramming

6

What really pisses me off about the way TDD is usually taught / demonstrated is how the REFACTOR part is simultaneously downplayed as "just refactoring" and yet at the same time it magically does all of the design for you. In my experience the developer still has to do all of the design, and that's far from being a beginner level skill. Conversely, every refactoring move has an inverse, and so refactoring by itself is agnostic to code / design quality. In most TDD demonstrations I've seen, the exercise is sufficiently small that the resulting design is either trivial, or was worked out beforehand, or is terrible (bowling scores kata, much?). TDD is just as difficult as good software design. Rant over (for today) 😎

33

11 Comments

This is my favorite book: https://lnkd.in/gZAsgEPt "What has more flexibility? Frequency encoded NN systems or the amplitude encoded ones? It is difficult to say, but we do know that both, biological and artificial neural networks are Turing complete [4], which means that both possess the same amount of flexibility. The implications of the fact that both systems are universal Turing machines is that even if a single artificial neuron does not do much, or perform as a complex computation as a single biological neuron, we could put a few artificial neurons together into an artificial neural circuit, and this artificial neural circuit will have the same processing power and flexibility as a biological neuron" (p.53).

1