Walid Badinini

👨‍💻FullStack Developer .NET/JS👨‍💻

[Walid Badinini @WBadinini]

@mattibarzeev @kentcdodds @matanbobi One of the advantages of using getByRole or getByLabel is that you’re also performing accessibility testing. Favoring these methods can help you spot missing accessibility in your components.

[Cory House @housecor]

A common mistake: “I don’t like that person, so I won’t agree with anything they say.”

Example: “I don’t like Uncle Bob. So, DRY is dumb”.

A person you dislike may have good ideas.

And a person you like may have bad ideas.

Separate ideas from people.

[Cory House @housecor]

You don’t need a daily standup. But you do need to communicate often.

You don’t need formal retrospectives. But you do need to regularly discuss improvement opportunities.

You don’t need sprints. But you do need to break work down and deploy often.

You don’t need a sprint review. But you do need to iterate based on feedback.

You don’t need a scrum master. But you do need to assure the things above happen.

[Programming Wisdom @CodeWisdom]

"There are only two hard things in Computer Science: cache invalidation and naming things." - Phil Karlton

[Walid Badinini @WBadinini]

A good one: "Everything is messy when it's not you code"

[Walid Badinini @WBadinini]

@housecor How do you deal with developpers how doesn't accept your comment's, and they take it personaly ?

[Walid Badinini @WBadinini]

@boredabdel FYI, Moroccan banks started developping their e wallets 2-3 years ago. It' not something new.

[Walid Badinini @WBadinini]

@housecor I have question about how the QA team do their manuel testing when you finished your part with a mocked Api because the api team still working on their stuff. Do we need to push the mocked api part ?

[Walid Badinini @WBadinini]

@arbaoui_mehdi I can't understand why there'are such framework's fan. What're their arguments ?!

[Cory House @housecor]

This advice applies to anyone with a job.

"A big skill, if you want to play for a long time, is just being honest in assessing how you're playing. If you wait until the coach tells you you're not playing good, a lot of times it's too late." - Jason Spezza, pro hockey player

[Walid Badinini @WBadinini]

@housecor What do you think about a PR containing much of refactoring unrelated to its purpose ?

[Cory House @housecor]

Using mostly divs may be easier for the developer, but it makes life harder for screen reader users, and fellow developers trying to understand the markup.

So, putting in a little extra work to chose the right tag isn’t just about professionalism. It’s an act of empathy.

[Cory House @housecor]

Historically, access to knowledge was a form of power.

Today, most knowledge is available for free.

So now, power comes from:
1. Knowing how to access relevant knowledge quickly
2. Knowing how to filter signal from noise
3. Knowing how to tailor the knowledge to my purpose

[Walid Badinini @WBadinini]

Sometimes, I feel like @housecor hear my thoughts and answer me ^^

[Cory House @housecor]

To get promoted, exceed expectations.

Be proactive.

Think bigger picture.

Take on more responsibility.

Identity and resolve quality issues (performance, security, accessibility, etc).

Avoid thinking “that’s not my job”.

Start thinking “where can we improve?”

[Walid Badinini @WBadinini]

A good habit I got from a previous mission, is to never commit a commented code, and if, for some reason you need to save it for later, the task ticket, in Jira for example, is your friend, you can put it their as a technical recommandation for next time.

[Cory House @housecor]

Being a developer requires balancing hubris with humility.

Hubris: “I’ve never done that. But sure, I can handle it”.

Humility: “I just finished it, but there may be a better way of doing this”.

[Cory House @housecor]

I strive to carefully review every pull request because it's the only way I keep the app's structure in my head.

This knowledge means I can spot and resolve architectural issues early. I can see inconsistencies. I can spot duplication.

Knowing the whole app is powerful.

[Cory House @housecor]

Thorough code reviews are the right thing to do. But there are selfish reasons to do thorough reviews too:

-Find new techniques
-Show leadership skills
-Practice giving constructive feedback
-Stay up to date on the app's structure
-Learn to think critically about code quality

[Cory House @housecor]

When a developer responds to every pull request with “looks good to me”, I don’t think “wow, you’re easy to work with!” I think “are you too busy to give me a real review with useful feedback?”

If every pull request is approved without comment, something is wrong.