@title[Home]
+++
How joyful your work can be? Why it is important? How often do you have such a joy? What can lead to truly joyful work day?
@title[10 things]
Which parts would it be?
Seems like it's absolutely necessary to know how to read through the language beforehand. But sometimes it's easier to understand something by playing with it. Even "wrong code" is a better place than no code at all.
We can express our ideas in a bunch of different ways and use different approaches to get better results.
Object-oriented paradigm, functional, declarative, parallel computing, event-driven etc
Software project development has it's own phases and it's own ebbs & tides. Also there are many researches on group dynamics related to teams.
We could use only "right" data structures and algorithms to express our ideas. But we see that "dirty way" shows good results too.
Which parts we want to join into one piece? In which order? I believe that those parts and it's relations could be clearly outlined for better cohesion.
Can you stop for a minute? For a day? Do you have slack time to come up with new ideas?
Are you listening to you self and to your colleagues? Are you patient enough? What have you learned from them? What can you give to them?
<iframe width="560" height="315" src="https://www.youtube.com/embed/3yRMbH36HRE?rel=0" frameborder="0" allow="autoplay; encrypted-media" allowfullscreen></iframe>
gitpitch.com/inesusvet/music-talk
fb.com/ivan.nesusvet