Doug Bradbury

A new Cypress.io + Qwik video: "Bonus 132: Prove the Qwik event handler download" https://lnkd.in/e-fZUf-N This is an example lesson from my full course https://lnkd.in/eGKeDH99

14

The number of characters that need to change to fix a bug is inversely proportional to the amount of time it takes to find the bug.

3

1 Comment

Jr. Devs, You need to start thinking outside the box when it comes to your career. I was talking to a friend of mine yesterday and they were telling me about a small business their children (12 and under) had started. I won’t reveal what it is to protect their small advantage. :) But basically, it's providing a simple service that takes very little time for very little cost. It's offering a convenience. Anyway, as he was telling me about it, it was so simple, so obvious, but something I would have never thought of on my own. I’m not really an idea person. I need something to start with, a clear problem to solve. I often need a pre-defined path to follow. Many Jr. Devs need to be less like me, trying to follow the pre-defined path, and more like my friend, looking for things other people might be missing, opportunities no one may notice. Think about ways you could implement what you are learning to help individuals, small businesses, local governments… virtually anyone; to fix a problem, meet a need, or simply make someone’s life easier in areas they may not have thought of themselves. The traditional route into development is clogged right now, so perhaps it’s time to look around and see opportunities from a different perspective. Find a non-traditional route to begin using your skills in a career that might look a little different from everyone else. Who knows, you just might stumble on the next Uber or Airbnb or maybe you just build a great list of clients who need simple work from a trustworthy developer. Take a fresh look at the problem and find a creative solution. #juniordeveloper #mentoring

14

1 Comment

We are (at least some of us) being dishonest, or at least negligent. "Hallucinations" from AI.... Seems to me we are either passing the buck, being lazy, or just... well... being dishonest. So AI gives us some information: * We don't review: then being lazy or negligent. * We do review, and kind of ignore, well... being dishonest. With all the breakouts about AI "they took our jobs!!! (Southpark reference - https://lnkd.in/gV-aJuDd)".... Maybe they will one day. But today, they are incompetent at least 10% of the time.... The responsible thing to do is review and consider before we use....

1

I just sent this email to #BigBasket #bbdaily about inconsistent billing. Some (like I) would call it fraud. I had a customer experience and fraud confrontation with #Flipakart a couple weeks ago. What's going on with me? Really... Is it me or them? When will they really get serious? I understand that there can be software errors. In digital world, or technically - a software, N number of things can break. But there are few things that cannot be compromised. OK, here's that email 👇 Dear Grievance Officer at Bigbasket, I am writing to bring to your immediate attention a serious issue regarding incorrect billing of products on my account between <redacted> and <redacted>. This matter is not just a simple error but constitutes financial fraud, which cannot be taken lightly. During the specified period, I noticed that the billing for one item (<redacted>) was inflated. For <redacted> milk, the correct billing was <redacted>. However, between <redacted>, both dates included, <redacted> was charged. Although I have been promised by the customer support that the additional amount has been refunded to my account, I am concerned that other customers might have been similarly affected. This issue likely extends beyond my account and could have impacted numerous other customers. I am also worried that these things might just be occurring and will continue to occur. Out of 100 customers impacted, a few may notice and the remaining may not even know that this happened. Bigbasket is making money in unscrupulous ways. Given the gravity of this situation, I urge you to initiate a thorough investigation into the matter. It is imperative that corrective measures are implemented promptly to ensure that all affected customers receive appropriate refunds. Additionally, robust measures must be put in place to prevent such issues from occurring in the future. Please provide me with detailed information on the steps you are taking to resolve this issue for other customers and the preventive measures you plan to implement to avoid such incidents in the future. I also intend to bring this matter to the attention of the concerned government authorities to ensure that appropriate actions are taken. I look forward to your prompt response and resolution of this matter. Trying to do the right thing Saket Modi

9

How many green squares do ya got? 🤨 When I sat down to talk with John Vandivier, we discussed employers checking into those precious green GitHub squares you were told to accumulate. Employers may not pay much attention to specific lines of code but... It's rare if they do AND potentially a very good sign. It means they were interested enough to dig deeper! So do you need to have a solid sea of dark green squares on your GitHub? Is it necessary to be able to land a job? What's your take? 👇Check the comments for the full video!👇 ---- 🎬 Check out Dev Leader on YouTube for multiple full-length videos weekly! 🗣️ Share with your network! #SoftwareEngineer #SoftwareEngineers #SoftwareEngineering

14

11 Comments

I recently facilitated a workshop where a classic "know-it-all" senior developer reluctantly participated. The goal of the day-long Kata Culture Intro workshop was to guide teams in discovering the benefits of TDD and Pairing through a hands-on, Coyote Teaching style collaborative approach. Predictably, this developer voiced common objections throughout the day to TDD, claiming it was unsuitable for complex problems, start-up environments, fast-paced projects, and his personal coding style. My responses aimed to address his misconceptions: Complex problems: I highlighted how TDD excels in these scenarios, actually streamlining the development and discovery process saving valuable time. Start-ups/fast-paced environments: I shared a relevant anecdote from our time at Premera, where we rapidly delivered 13 functional prototypes (these were more than just prototypes) while simultaneously learning Azure. Jim Speaker remember that? Personal coding style: By the end of the day, the developer surprised me by acknowledging, "I had the wrong idea about TDD. Seeing it in action, I realize it could be a huge time-saver for us." While I'm constantly seeking out new methodologies, TDD still remains the most effective tool I've found. When combined with pairing or ensemble programming, its impact on software development is undeniable. TDD is easy to gain awareness of, deceptively challenging to gain proficiency with, and very rewarding/timesaving to have gained fluency with. #TDD #TestDrivenDevelopment #SoftwareDevelopment #Programming #Coding #Agile #ExtremeProgramming #Pairing #EnsembleProgramming

186

50 Comments

Not specific to coding screens so forgive me for going off-track but I feel like there can be a "you won't always have a calculator" discussion that might be interesting. In regards to open-book or closed-book, it is difficult to remember everything so referencing something you might have forgotten isn't uncommon but there is a distinct difference between refreshing your memory and searching for a solution. However, being able to research effectively is also a great skill. With access to this information so readily available and the growing popularity of AI, I can definitely see engineers trending toward having less technical fundamentals and critical thinking in favor of yielding quick results. Is it efficiency or laziness? Will it be damaging? I'm curious how it will affect the industry.

3

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

"No More Blue Fridays" and eBPF, it's just a one-minute reading: https://lnkd.in/gAAmNU4D if you haven't seen it. That's precisely what I speculatively said to my colleagues, without even reading anything about it, answering their question about how that could happen: "BlueFriday was most likely triggered by the ring0 kernel driver accessing the invalid memory. It's hard to say without knowing details, but Ring0 could be the only way on Windows to access a particular functionality, like Network Stack." Undoubtedly, eBPF is a great tech, but is it a silver bullet? Can it replace Ring0 or kernel drivers? I do not think so. It's excellent for its niche, but is it safe? No. Is it safer than kernel drivers? Yes, it is way safer (as well as any other indirection layer that provides an infiltrated interface).

2

Just a short rant... Quality Assurance is not optional. Software Developers checking their own work is good. Unit tests are swell. But none of that is ASSURANCE. You're taking the same people who had the misconceptions that caused the bugs in the first place and are asking them to confirm the code works according to those same misconceptions, and write test code that confirms those misconceptions. And when the user finally rejects the work, now you have the application AND the testing code to fix. The cost of having developers test their code - or each other's code - is far higher both in cash and schedule than having a parallel QA testing team checking the work. Pay the developer to write the code and debug it to a working happy path, and then pay a tester to run down the bugs at half the cost. Say that the average verification effort is 25% of the development effort, that's a 10% savings right there, and the resulting work product is better and everyone involved is happier. Every time I have stood up a development team, my first hire is the principle developer (usually me) and the very next hire is a tester to check their work. Grow your dev team and hire a tester for every 3-4 developers. This used to be common practice, but now this myth prevails that you can automate your way out of having the work reviewed by an independent human perspective. We had white-box unit testing in the 90s too, ya know. We still had QA! And you know who makes awesome testers? Aspiring Junior Developers. You have a software development organization that you intend to grow and keep around for a few years? Today's junior testers can become your most loyal, knowledgeable and valuable senior developers in 4 years. Plant seeds. Grow people. THAT is how you build a 10X development organization.

25

7 Comments

I've spent the past 12 years helping orgs move from a dev-ops team to a dev-ops mentality. One thing I've refined and learned with others along the way is the concept of a "Dev Ops Contract". It's a concept so simple, it's often overlooked, but some powerful benefits are: - Clear understanding of what software requires to be operational - Reduced complexity in runner configs (github actions, AWS codebuild, etc...) - Developer autonomy - Parity with local and remote task execution And more if you're interested: https://lnkd.in/gyRmQPq9 Is anyone else out there decoupling their CICD from their services in a similar way?

7

Observation: 9/10 SWE's quit at “reading the docs”. Cut through the BS with this easy trick: Take action and build. Writing code is 100x easier than the docs make it sound. “Reading the docs” gave me crazy imposter syndrome: -Git -WPF -Kafka -OAuth -Angular -GraphQL -RabbitMQ -Kubernetes In ALL cases, I conquered my fears by building. Except for WPF. I gave up on that. And Kafka, that's for another day. Forcing yourself to build/code/deploy melts analysis paralysis. Then you'll say "oh that was pretty easy". Trust me, we aren't building rockets. Practice AND Study build true mastery.

22

1 Comment

First post in my Ruby concurrency series is up! "Your Ruby programs are always multi-threaded: Part 1" The series starts off by discussing some common threading issues to look out for, and why they work the way they do in CRuby's internals 🧵. https://lnkd.in/em4Xe4xB

13

1 Comment

🙋 “What in the world are these for?” This is often the first question when you look at a list of feature flags. 🧠 💬 Capturing intent is one of the more difficult things for developer tooling. Making comments required and having a template, such as a commit message, can only go so far when feature flags need to be changed quickly. ⚠️✏️ As stale flags are not cleaned up, it is even more difficult as flags with the same name pop up and add to the confusion. 𝘱𝘦𝘳𝘴𝘰𝘯𝘢𝘭-𝘥𝘢𝘴𝘩𝘣𝘰𝘢𝘳𝘥 vs 𝘥𝘢𝘴𝘩𝘣𝘰𝘢𝘳𝘥-𝘳𝘦𝘸𝘳𝘪𝘵𝘦? Which will fix my outage or make it worse? Code understanding is one approach that will make a huge difference. Using the advancements of LLMs and tools like Sourcegraph's Cody, a user could start to understand what a flag does in a product, and if the consequences of their change match their intent.

11

Building off of yesterday's fictional book announcement (https://lnkd.in/gBAU8nyZ) Here's the next book in the Nate Taylor Management Series.

45

16 Comments