Explore >> Select a destination
|
You are here 
|
www.marclittlemore.com | ||
| | | | |
www.electronvector.com
|
|
| | | | | Over the years I've worked in and with many different firmware organizations. In my experience most people are really trying to do their best but I see many struggling with the same, common problems of organizational maturity. When an organization is mature it makes disciplined use of best practices and tools to regularly and continuously deliver high quality firmware. When an organization is immature, things are done in an ad hoc (often reactionary) way. Successful results are not easily repeatable and it is often the responsibility of just one or two individuals to try to hold it all together. | |
| | | | |
blog.coryfoy.com
|
|
| | | | | ||
| | | | |
scastiel.dev
|
|
| | | | | By focusing on learning, providing constructive feedback with a positive tone, and embracing the opportunity to contribute, junior developers can make valuable contributions to code quality and their own growth. Code reviews are essential for skill development and fostering collaboration within development teams. | |
| | | | |
www.softdevtube.com
|
|
| | | Computers are orders of magnitude faster than when most of us started programming and yet a lot of software runs much slower than it should. Nobody likes progress bars. Slow code provides for a horrible user experience, drains batteries faster, and increases our cloud bill. This session explores some of the reasons why software is | ||
