JFBCodes on Youtube - Jason Fleetwood-Boldt

Thu. Nov 21st, 2024

demonstration of how to navigate to /Applications/Utilities

macOS navigation to /Applications/Utilities

https://school.jfbcodes.com/learn-unix-basics-fast

Unix Basics Fast (Intro)

Focus on fixing flaky tests. #tdd #software #engineering #developerexcellence
https://www.tiktok.com/@jfbcodes

Flaky Tests 4 - what to do about tests that fail at certain times of the day, week, month, or year. https://jfb.dev/

Flaky Test 4: Time Sensitive Conditions

If the test run order makes some tests flaky, then you don't have hermetic tests.
https://jfb.dev/

Flaky Test (3 of 5)

The Agile Premise

You may have heard of the iron triangle of project management:
"Scope, cost, quality. You can't have all three, so choose only two." This means that:
• If the scope is large and the cost is cheap, then it probably won't be very good
• If the scope is large and the quality standard is high, then it will be expensive.
• If you deliver it to a high-quality standard but cheaply, then can only have a very small scope.
Scope, cost, quality — you can only pick two without negatively affecting the third.

In agile software development, we have an answer to this question: and here’s the agile answer.

We always the best quality— we never want to compromise on quality. That’s a lever we picked to stay in place.
Cost (which is the same as time, assuming people get paid by the hour or by the day) is a lever we manipulate through the scrum process by doing sprints with a short fixed timeframe. That’s it — we don’t plan too far ahead, we don’t plan 3 or 6 or 12 months out— instead, we work a little blind to long-term considerations and focus only on the immediate future of the next sprint.

And that leaves us with scope. Scope is the only lever left and the only thing we can do at sprint planning is to carefully decide what is a reasonable scope for 1 sprint’s worth of work.

So in essence, when we’re doing agile scrum, we never really talk about quality or about time. Because quality is fixed because we always want the best quality, and time is easy— it’s just 1 sprint (either a week or two weeks or whatever your team uses). So we don’t need to discuss those things, we only discuss scope.

If you’re in a business that’s writing software planning out too far in advanced or if your boss wants to dictate the time and dictate the scope, that is not an agile process (in fact, it’s waterfall) and you probably aren’t using scrum the way it was intended to be used.

So again, just worry about the scope and work sprint-by-sprint to focus on highest priority needs.

https://jfb.dev/

The Agile Premise

Race conditions in flaky tests. https://jfb.dev/

Flaky Tests (2 of 5): Race Conditions

Lets talk about flaky tests. #developerexcellence #automatedtesting #tdd #code #codecoverage #software #agiletok #techtoktips

Flaky Tests (1 of 5)

Please see the accompanying blog post:

https://jasonfleetwoodboldt.com/courses/stepping-up-rails/ruby-arguments-equal-signs-colons-splats-double-splats-explained/

In this video I’m going to explain how method arguments work for the Ruby programming language. If you’re new to Ruby or you’re working on codebase you haven’t worked on before, it can get a little confusing seeing all of these symbols in Ruby method definitions and invocations. Many people who might be used to simpler programming languages see these colons and splats (a splat is another word for a star or asterisks) and are probably left wondering — what do all these things mean. Part of what is confusing is that Ruby started its life having only positional arguments. Then in Ruby 2, keyword arguments were introduced. On top of that, we have this special thing called rest arguments (that’s what you use the splat for) and then we have keyword rest arguments too. So this video will be a little long because I’m going to show you all of the rules. And it turns out that because of all the different options between positional and keyword and rest arguments, there are 14 different examples. So I’ll go through each example one by one to explain every part of arguments in Ruby.

This video covers modern Ruby, and explains which versions of Ruby these concepts were introduced.

- Positional Arguments
- Positional Defaults
- Rest positional Arguments
- Keyword Arguments
- Rest Keyword Arguments
- Keyword arguments Defaults

The Pyramid of Learning to Code:
https://jasonfleetwoodboldt.com/courses/the-pyramid-of-learning-to-code/

Ruby Arguments: Equal Signs, Colons, Splats (*), Double Splats (**) Explained

Load More... Subscribe

Latest Posts

TikTok

https://www.tiktok.com/@jfbcodes

You missed

Stupid Simple Scrum using ClickUp

March 23, 2024 Jason

Allowing Chromedriver on MacOS (This version of ChromeDriver only supports Chrome version XX)

February 3, 2024 Jason

GDG Web Dev Fest @ Google NYC (18 Jan 2023)

January 24, 2023 Jason

React Meetup @ Wix Playground (17 Jan 2023)

January 18, 2023 Jason