Takeaways

Communicate with the scrum master! Not just updates and questions, but also clarifications and preferences about subtasks, work styles, etc.

Some projects have major pivots and changes even after a lot of work - that's just the way it is sometimes.

Takeaways

Document your classes and methods.

Have some kind of template or guidelines for how classes and methods will be organized.

Takeaways

Style the static element - then animate it or make it appear/disappear.

Sometimes you'll have to redo entire sections of code, rework classes/ids, or do other major refactors. It's worth it.

Getting the projects menu/content to update and display correctly was a lot of work! It took three rewrites and consulting two people, but I finally have the results I want, and I understand the code behind them.

When writing webpage scripts, console.log() is your friend.

Takeaways

Have a dedicated scrum master, whose minimum job is task assignment. Don't just do it as a free-for-all.

Always, always communicate when distributing tasks.

Do regular stand-ups, or otherwise have some record of what you're working on.