The Engineer Uniform, Vegetable-Themed OSS, and Other Must Reads

Erran Berger
3 min readbeginner
--
View Original

Overview

The article discusses various insights from LinkedIn engineers, focusing on the importance of workplace attire, software development practices, and the significance of innovative tools in web development. It highlights several must-read pieces that cover topics ranging from coding practices to mentorship.

What You'll Learn

1

How to effectively address frustrations in coding without starting over

2

Why the choice of workplace attire impacts innovation culture

3

How to utilize web development tools like Broccoli.js, Celery, and Cucumber

Key Questions Answered

What are the implications of workplace attire on engineering culture?
The article discusses how the shift from formal attire to t-shirts and hoodies reflects a culture of innovation among engineers. It emphasizes that this casual dress code is essential for fostering creativity and collaboration in tech environments.
What should engineers consider when feeling frustrated with code?
Engineers are encouraged to avoid the temptation to discard problematic code and start anew. Instead, they should focus on solving existing issues, which can lead to greater satisfaction and efficiency in their work.
What are Broccoli.js, Celery, and Cucumber in web development?
These tools are metaphorically referred to as vegetables in the article. Broccoli.js is a build tool, Celery is a task queue, and Cucumber is a testing framework, all of which are essential for modern web development practices.

Technologies & Tools

Some links below are affiliate links. We may earn a commission if you make a purchase.

Frontend
Broccoli.js
Used as a build tool in web development.
Backend
Celery
Used as a task queue for managing asynchronous tasks.
Testing
Cucumber
Used for behavior-driven development and testing.

Key Actionable Insights

1
Embrace a casual dress code to enhance workplace innovation.
Adopting a relaxed attire policy can help create an environment where engineers feel more comfortable expressing their ideas, ultimately fostering creativity and collaboration.
2
Focus on solving existing code issues rather than starting from scratch.
Addressing problems directly can lead to more efficient solutions and a deeper understanding of the codebase, which is crucial for personal and team growth.
3
Incorporate tools like Broccoli.js and Cucumber into your development workflow.
These tools can streamline your development process, improve productivity, and enhance the quality of your code through better testing and build management.

Common Pitfalls

1
Starting over with code when faced with frustration.
This approach can lead to wasted time and missed opportunities for learning. Instead, engineers should focus on troubleshooting and refining existing code.