Terms

7. Terms (neologisms)
.
To bikeshed or Bikeshedding: Arguments that are irrelevant to the program. Unnecessary work.
.
Yakshaving: all the work that is not the core of what you are trying to solve, but you still have to do it to get to the point. Necessary but not the main work.
.
Boilerplate: All the paperwork or set of files you need for a project. Use tools like Create React App to get the Boilerplate and start a React Project. Files like red-meats and json are part of the boilerplate for a project.
.
Scaffolding: Set of files or functions you bring up at the beginning, so you can get going and that you replace as you build more complex versions of those files.
.
Onboarding: When you bring a new employee onboard the team. It’s the series of steps you take to help them get started with the code base, tools they need to use, and understanding the system before they can contribute.
.
Dogfooding: (eating your own dog food). If the tool you’re working in, say a project management tool, is being used as part of the process of building that tool, then you’re doing dogfooding. Test your products in real-world usage using product management techniques. Hence dogfooding can act as quality control, and eventually a kind of testimonial advertising.
.
Rubberducking: Reference to Sesame Street when Ernie is taking a bath and has a dog in his hand, and he is telling him all his problems. When you have a problem you don’t know how to solve you ask a coworker or friend to come and start telling them all the details of your problem and as you do that is claims clear in your head and you figure out the solution, sometimes before you finish explaining the problem.
.
Green field: When you start a project with nothing before it, you’re starting on a nice green field of pure grass. There’s nothing else there you have to deal with and you can focus on the problem and you solution you want to build.
.
Brown field: Contrary to the green field, you have to deal with an existing system, you have to fix all the problems it already has, it slows you down, you have to deal with what the users already expect. That’s of the known as Technical debt, which is when past developers of the system took some shortcuts and made some decisions that you’re paying the price now.

I love using Rubber Duck Debugging 😅 🦆

Before statring the sesh i had to do some Rubberducking in order to make my ideas clear, the complete programm had several issues and bugs to attend, it was no Green field afer all, but still couldn´t make any single line of code that wasn´t Bikeshedding, so by pairing with a mate, we both manage to pay some of the Technical debt we had

Bikeshedding

– "No! the button has to have a width of 80px 🤬
– "Hey! you’re bikeshedding, stop arguing and do the functionality of that button.

Yakshaving

– “Have to do the Landing Page bothers me, that really matters is the management interface”.
– "It’s a yakshaving work, but everything is part of.

Phrase: Yesterday I onboarded a new programmer to help me pay the technical debt in the codebase. After a session of rubberducking we decided that we need some yakshaving in the repo to continue.

😅

In our last project, we were yakshaving a lot in order to be familiar with the codebase, I prefer green field projects, but my manager wanted me to solve some technical debt that my coworkers left. It was part of my onboarding process.

bikeshedding:
arguments that are irrelevant to the program
yakshaving:
it’s the opposite of bikeshedding: make things that aren’t the core of the program, but it’s important make them in order to achieve the goal of the proyect
rubberducking:
when you have a problem and don’t know how to solve, you ask a co-worker and start telling the details, and while you’re doing that you figured out the solution sometimes you finish the problem, that’s a good debugging technique.
dogfooding:
your using your own tool as part of your work
boilerplate:
legal terms or files, example: readme file
scaffolding:
they’re a set a files and functions that you bring up at the beggining then they let you replace and build more complex files.
green field:
generally a new proyect
brown field:
deal with an existent system, users, legacy code and other aspects knows as technical debt
technical debt
In project management or software development, technical debt is a metaphor for the cost or consequence of prioritizing delivery over performance. For project managers, technical debt can accrue when you ignore best practices and requirements to meet project deadlines

We talked a lot about used to describe the teams you’re working with and the technologies you’re using.
Software development has a lot of neologisms or completely new words and terms that have been developed for our particular field of work.

Bikeshedding
It’s about arguments that are irrelevant to the program.
Ex: like wheter a button should have two pixels in this side or not. That’s a minor detail that’s not really important. If I say this, I’m “bikeshedding”.
Bikeshedding is irrelevant work.
.
Yakshaving
It’s the work that you need to do if you have to milk a yak.
Yak are those big animals that live in Tibet that have lots of hair around them.
If you need to get milk out of the yak, you need to do a lot of shaving.
Yakshaving is all the work, thai is not the core of what you’re trying to solve, but you still have to do it to get to the point.
Yakshaving is necessary work.
.
Boilerplate
I’'s basically the standard text or the standard set of files you need for a project.
There are plenty of tools like for example “Create React App”, that will provide you the boilerplate to start a React project.
.
Scaffolding
It’s not the same as boilerplate.
It’s a structure you put around the building when you’re working on it so that workers can reach the upper levels and move around the building.
On a software system, scaffolding is a set of files and functions that you bring up at the beginning, so you can get going.
.
Onboarding
When you bring a new employee on board the team.
.
Dogfooding
It means you’re using your own tools as part of your work.
.
Rubberducking
When you have a problem that you don’t know how to solve, you ask a coworker or a friend to come, you start telling them all the details of your problem, and as you do that, your head and you figure out the solution; sometimes before you finish explaining the problem.
It’s one of most useful tool you’ll find.
.
Green field
When you start a project with nothing before it, you’re starting on a nice green field of pure grass. There’s nothing else there to deal with.
All you need to do is worry about your problem and the solution you want to build on top of it.
.
Brown field
It’s when you have to deal with an existing system. You have to fix all the problems it already has. It slows you down. You have to deal with what users already expect.
.
Technical debt
It’s when the past developer of the system took some shortcuts and made some decisions that you’re paying the price.

This will be a nice opportunity, 'cause we are going to start a greenfield project, and it means no yakshaving, and more time for rubberducking in the project I’m stuck in.

🐮 Terms

**Bikeshedding**

Arguments that are irrelevant to the program, like whether a button should have two pixels on some side or not

**Yakshaving**

• It is the work you do if you have to milk a yak (Animals that live in Tibet and that have lots of hair around them). If you need to get milk out of the yak, you need to do a lot of shaving.
• Is the work that is not the core of what you are trying to solve, but you still have to do it to get to the point

<aside>
💡 Bikeshedding is irrelevant work, yakshaving is necessary work, but that has nothing to do with the core of what you want to achieve with your system.

</aside>

**Boilerplate**

• Come from a legal term, it is basically the standard text or set of files you need for a project
  • There are plenty of tools like, for example, create react app that will provide you the boilerplate to start a React project

Scaffolding

• Is a structure you put around the building when you’re working on it so that workers can reach the upper levels and move around the building
• Scaffolding, on a software system, is a set of files and functions that you bring up at the beginning, so you can get going and that you replace as you build more complex versions of those files

**Onboarding**

• When you bring a new employee on board, the team
• It becomes a verb, as it’s a series of steps you take to help them get started with your codebase, with the tools you need to use and understanding the system before they can contribute

Dogfooding

• When you eat your own dog food
• It means you’re using your own tool as part of your work

Rubberducking

• When you have a problem, and you don’t know how to solve it, you ask a coworker or friend to come
  • You start telling them all the details of your problem and as you do that, it becomes clearer in your head

Green Field

• It is when you start a project with nothing before it, you are starting on a nice green field of pure grass, there’s nothing else you have to deal with
• All you need to do is worry about your problem and the solution you want to build on top of it

Brown Field

• It is when you have to deal with an existing system, you have to fix all the problems it already has, it slows you down, and you have to deal with what users already expect

Technical debt

• It is when past developers of a system took shortcuts and made some decisions that you are paying the price now

• to bikesheed / bikesheedding: we talk about arguments that are irrelevant to the program
• to yakshaving: is the work that is not the core of what you are trying to solve, is necessary.
• boilerplate: is a set of files you need for a project, the necessary or mandatory files that you need (readme, package.json, etc…)
• Scaffolding: Son otros archivos que los vas cambiando para situaciones más complejas de la aplicación
• Onboarding:
• Dogfooding: Cuando usas tu propia herramienta como part of your work
• Rubberducking: explain for to clean your head
• Green field: Nada, todo desde 0 y tienes el camino libre para construir lo que requieres.
• Brown field: Ya exite, tienes un sistema delante de ti, y no puedes tener toda la libertad que quisieras.
• Technical debt: Deuda tecnica

Client’s requests are tough to complete on this brown field dashboard project because there is a lot of technical debt. Our team took some time on bikeshedding just because of the graphs’ colors, by the end of the day we finished doing yakshaving.

After watching this module I’m thinking that our onboarding process need some fixes, because it doesn’t include information about some technical debt. We need to improve our documentation, and maybe include in the welcome kit a rubber duck for all of the new member. 😉

This project is a GREEN FIELD IN but at some point you can be YAKSHAVING i’ts going to be challemging and maybe more if you´re now ONBOARDING, anyway, don’t worry you will be building the bases and SCAFFOLDING to get a better result!

This is my sentence using the terms

I need to create a Boilerplate for Scaffolding the project. The good part is that we have a green field and we just need Yakshaving a little bit.

A CODING STORY
I had a pointless discussion or a bikesheding with my co-worker
last week, so to speak. That’s one of the reasons why i don’t like this methodology of paring, it is a totally waste of time. Anyways, we were trying to code the best and most beautiful calculator in the market, we had full green field to do so, but then, we struggled and stucked on the project. We wanted to add as many things as possible to the code that it seems as though we were yakshaving.

I was talking with my peers about the yakshaving that I have to do due to the boilerplate code and the project’s technical debt, and I found that I could scaffolding it. I thank my colleagues for helping me as rubberduck and continue coding.

I think I have to learn to do a rubberducking properly to come out with good solutions faster.

When I am faced with a new project, what I usually do is create a boilerplate project. I assess the tasks, considering the yak shaving and avoiding getting caught up in bike shedding discussions. When I encounter an issue with the code, I tend to practice rubber ducking. This technique helps me organize my thoughts and often leads to new ideas or different perspectives on the problem.

akshaving reminds me of an episode of Malcolm in the Middle where Lois asks Hal to change a light bulb, and Hal ends up doing mechanical work on his truck.

I started a brown field project the last week, my team were in charge to onboarding me, I was so excited but only took a few minutes of reading code to realize all the yakshaving that I had to do, So I did what every Junior developer had to do in that situation…I started with the boilerplate.

What do you think? 😃

I have experience in a green field project and I try to use a boilerplate structure to reduce the tecnical debt, finally I do Dogfooding.

I use a boilerplate in a green field project to try don´t have technical debt from the beggining.

Very impressed with Yakshaving and Bikeshedding terms, very useful to feel better with the English!

I’m doing some rubber-ducking because I have to work with some boilerplate that I don’t understand, and during the onboarding, I hadn’t the chance to explore all the scaffolding of the brown field that I’m currently working on.

Aprendí varias palabras que había escuchado pero no sabía exactamente, qué significaban.

I need rubberducking, at least with two partners, I think I doing Doogfooding, i would like to that was an Green field project , but no.

I realize that I often do rubberducking.

in my old team the project was completely green field, but during this time the technical debt started due to lack of experience

This is the sentence I created using the terms:
Right now, I am working on a green field but I do not have boilerplates in my computer. So it is possible I start rubberdocking, since I am onboarding the new junior programmer tomorrow.
What do u think?

During the onboarding, people explain to me that, I don´t have to be worried about brown field or to much technical debt (from other developers), becouse we are starting a new project, and for me, it will be as a green field

At the Onboarding, they teach me how to get a Bolingplate because I had Yakshaving before get going

I have to assist to the sesh with some docs and recs to the new project, where we will start a green field product, then I could need to make dogfooding in the next moths, taking account that there will be some bikeshedding due to possible technical debt.

I appreciate if something is wrong, please tell me:

One of the steps in onboarding is initializing the green field for the real project. After one week and a half is necessary dogfooding in order to know if the team has the same idea and review the progress of each member about done working. At the same time, we have to review the boilerplate to update the real status and avoid brownfield.

I Love it; Rubberducking LOL

Recently I switched jobs and the onboarding process wasn’t fun at all had to figure out most of my duties by myself, finding a lot of technical debts and a large brown field to deal with.

On the Onboarding process the tema explain me the boilerplate of the project and the yakshaving that we have to do before attacking the technical debt

I just posted my last project started from a boilerplate with REACT App. I spent lot of time bikesheding and jackshaving so if someone wants to improve it is a green field.

Once I get to a new company, I’ll have to begin my **onboarding ** process, let’s hope the company takes me to a green field without technical debt, where I can work comfortably. I don’t mind yakshaving, cause it’s something part of the job

Most of the time I have to work in the brown field in the design of the electrical substation.

When I built my first greenfield web application by myself I didn’t know where to start so I asked for help from a friend and he suggested starting by implementing a boilerplate. After figuring out the meaning of such a term everything was easier. During the development process, I invest a lot of time in making yak shaving work dealing with the design of my landing page. If you are trying to fix a problem related to your code, the best you can do is to apply the rubber-ducking technique, this means understanding the whole problem by describing step by step the flow of your code,

Every developer wants to start a green field project but in mostly cases they found brown field projects when the onboarding starts. Use the rubber-ducking technique to face those projects.

In order to be part of the challenge I had to go through an Onboarding process,
but just in the challenge I found myself lost with some tasks, so I used the Rubberducking technique with my friend

Excercise

We have a new member in our team. We are going to do the onboarding in one hour. I will be able to explain all of the things, but if you need help, you can do rubberducking with your co-workers all the time.

I tarted an application green field and decided use vite for its boilerplate of React, I focus on yakshaving react hooks and after in the bikeshed style of CSS.

No Yakshaving, no money 💰😂

Bikeshed: arguments irrelevant to the program
Yakshaving: necessary work
Boilerplate: standard text you need for a project readme
Scaffolding: set of files you bring at the begening
Onboarding: new teamate
Dogfooding: use your own tool
Rubberducking: tell your problems you don’t know how to solve

👉Ex: I’m pretty nerveus for onboarding the Platzi team. I’m scared to bikeshed instead of yakshaving at my work. I rubberduck this to my colleagues, and they told me, that if I have worked in Python before I can dogfood old code. Also, recommend to keep in mind all the scaffolding and boilerplates and asure me I’ll be ok

Scaffold (programming)
Scaffolding, as used in computing, refers to one of two techniques: The first is a code generation technique related to database access in some model–view–controller frameworks; the second is a project generation technique supported by various tools.

-Wikipedia

Thanks to the Technical Debt we have work!

During my interview, the project’s leaders told me that there was a lot of green field projects, during the onboarding my crew told me that they build boilerplates to quick start working on, but also told me that since the projects are in an early stage often I’ll dogfooding, so far I’m doing a lot of yakshaving in order to do the work.

my boss just star a green field project, im the sennior how leeds the team so i have to yaksashing a lot, its tired but to be honest doesnt matter, becuase a i prefer than be in brown fild and pay all the tecnical debts.

Always our developer team prefer to work on green field projects over brown field proyects , because brown field projetcs commonly have a lot of technical debts, but we dont worry about it so much, becouse we are a very strong developer team identifying bikeshedding, and we yakshaving in time.

Addiotionally we use to dogfooding with or own products, using them as external an internal process and benefits, for example one of the tools that I wrote is a scaffolding tool called Pscaff that can helps, no matters what programming language.

You can check it from :
https://www.npmjs.com/package/pscaff

I thinks one of the most common mistakes of new developers is when they are onboarding they always do bikeshedding even if the project is a greenfield. However rubberducking always helps.

I didn’t have a proper **onboarding **to the project, and because it is a brown field, I’m struggling with a big technical debt. Rubberducking has been a great tool to pay the interest 😄

Yesterday we hired a new developer, and I onboarded him, then he helped me to finish to pay the technical debt of a project I was working on. When all that was completed, we started a green field project, but since it was completely empty, I was kinda struggling with some specific solution, so I talked again with the new employee and after a session of rubberducking we were able to find the necessary solution.

i am Rubberducking of my compa-nion jajajajj, ni se si lo escribi bien ajajjajjajaj, pero en si soy el patico ajajajjja

Exercise

I wanted to start a green field project, so after all the yackshaving I found a brown field project full of bugs and technical debt I hopefully could solve after a rubberducking sesh.
I hope it is ok🧐🥺

(4-terms-Challenge)
My brother offer me a job for doing all his yakshaving and boilerplate in design, basically, an assitent, rubberducking with a friend I decided decline, I rather start with a green field.

Last year I came to this company, I expected to work in a green field but all I got was a brown field. The first days were tough because I paid a technical debt. But that doesn’t matter because everytime when I asked for help, I ended up doing rubberducking.

My Example
The sprint hasn’t be productive because it was showing up too many bikesheddings, it is a green field. Now i need to put up all scaffolding and to make a summary with my worries for meeting tomorrow and so new IC’s have a good onboarding.

Exercise

The project we take has a lot of technical debt, so we have onboarding a new developer to help us with this brown field. It was weird at first, she does a lot of rubberducking with unanimated objects, but we got use to it.

I really thought that it was a yak shaving, but after some minutes of a rubber duck with my mate, I realized that it’s only a bikeshed

I will have a difficult onboarding process because this old project is full of technical debts and my manager love the bikeshedding

I only knew Scaffolding and Onboarding. Very interesting vocabulary!

I was in sesh with my teammates and we got bikeshedding a long time until we started our project with boilerplate code that would be the perfect green field we needed to avoid yahshaving.

When I entered to the company I didn’t have any piece of onboarding, now I’m dealing with a brown electrical field

My phrase:

The staff engineers got stuck on a bug that the PM found while dogfooding. So I benefit and used that time to onboard the newbie and taught her how to use scaffolding code to start the E2E testing without the dev’s codebase.

That example sentence at the end is exactly what my job is 🤣

Example:
During the onboarding they suggested me to use rubberducking if i ever find myself in a yakshaving situation

• I spoke with my colleage because he was bikeshed, he was creating a Modal but the Modal was already created.

• I started my Boilerplate with Create React App and I was starting Scaffolding two week ago.

• My boss held a meeting because we needed to do an onboarding for my performance

• With the previous Senior of the project, when I asked about a process, often I rubberducking.

today in lunch time, I expected to solve some complicated issues I’ve been finding in the recent project, so i called two friends in order to rubberduck but instead we ended bikeshedding about the database we are going to implement

I don’t know about the term “RubberDucking”, I had used it before but did not know about it. My current stack is Ruby on Rails, and the term Scaffolding it’s very familiar to me. Right now I am onboarding in my new work, and all my tasks are relative to “Brown Field”.

a boilerplate will be made in Angular for a news project, starting from green field, where little by little the initial scaffolding will have prompt modifications.

I like frameworks because they give you very nice boilerplates and you don’t have to worry about bikeshedding