This post is about giving some tools and advice to junior developers and Boot Camp students.
It is just in Italian for now.
I hope I will have time for traslate it soon.
“The pandemic accelerated many trends, from streaming, e-commerce, and food delivery platforms to the widespread adoption of remote work.
But instead of taking advantage of this opportunity to improve how we work, most organizations simply took their offices online, along with the bad habits that permeated them.
A move to a better way of working remotely is desperately needed.
If your digital transformation is going to be successful, you need to give your employees the right tools and systems to work in a digital, distributed, virtual environment.
However, digital tools are only as effective as how effectively you use them, and alignment between managers and employees on remote work best practices will be critical to the success of any digital transformation initiative.”
(reading time 15 min)
Some time ago I wrote this tweet:
I’d summarize it like: Thinking JS has classes is like believing the engine of your car has real horses in it. I hope I got it right 🤓
Reading the You Don’t Know JS (YDKJS) book series leaves something inside you, especially when you have been in the front-end dev world for so many years.
It is a mix of amusement, inspiration, and sense of chaos about what web dev is, and what it has been for Javascript development in this specific case so far.
So sometimes you want to throw some message in the air, to externalize such feeling.
I personally found what I tweeted, quite significant so I decided to share it in other places, included Linkedin.
There a guy, front-end dev like me, showed his appreciation for my post and suggested to read a post he wrote on the topic.
I read it very carefully, this subject passionates me and it was a quite interesting post.
But at the end, the way the issue was tackled gave me this feeling, it was saying something like “ it would be interesting in theory, but do it this, instead, because everybody does it this way/this is the real trend”. Continue reading
When I worked in an office environment, I could be passive about social interaction because it was an inherent part of my day.
In a remote world, you have to be intentional about in-person socialization.
One of the best things about working remotely is that it leaves me the social energy for the times I want.
Prioritize your social activities, because they are a form of self-care.
An activity of National Research on Innovation about smart working in Italy.
Very interesting view on the internal perception about privilege and potential issues on the carrier on the other hand.
There is a constant in all this case studies, that is the fact that smart working spotlight the weakness of a company, giving the opportunity to improve and fix a lot of aspects. That’s why it could be a great opportunity as also a great cultural obstacle to overcome.
The idea of working five days a week with two day weekends and a few weeks of annual holiday is just something people accept. For some reason, it is considered set in stone by most companies. There is no reason this can’t change. In fact, it would benefit everyone if it did.
As Larry (Page) said: “The idea that everyone needs to work frantically to meet people’s needs is just not true.” We all need to work smarter, not longer.
Uk Government experience, very useful example of Countries that are started an innovation process in the way of manage work and resources, for several years now and with a relevant success.
The Government Hubs Programme will reduce the government estate from around 800 to 200 buildings by 2023, saving approximately £2.4 billion over 10 years. These spaces will support new and developing ways of working, allowing staff to work from a variety of locations, including hubs.
Very interesting post about a real hot topic, that could be so determinant about the quality of the service delivered.
It’s no secret that developers and project managers don’t always see eye-to-eye. In fact, many developers will tell you that their PM simply sucks.
While these sound like surface level complaints, they represent the core problem: disconnect between software engineers and project managers.
Interesting? Get a free notification when a new post is out.
