Great post by Paul Jansen at TIOBE Software. In my experience, this starts with the right mindset and values driven from the top.
The right values and mindset drives tooling and process decisions, which enable developers to solve problems earlier in the development cycle and prevent them becoming blockers late in the cycle.
A lot of my customers work in the embedded field, which puts additional challenges on tooling. RTOSes, cross compilers, debuggers, hardware boards and the like.
Luckily, proper use of infrastructure technology such as containers and Kubernetes allow teams to encapsulate that complexity and make it easier on individual developers removing the need to install and maintain tools locally
Modern software development teams have 0-effort onboarding workflows for their engineers: Clone a repo, open in container, create a branch, code, submit changes, test in pipeline or local, create a merge/pull request, review and merge.
I am the lucky guy who gets mails asking to unblock failing software quality gates all day long. Usually such mails are dropped in my inbox at the end of a working day, or in the middle of the night, or why not, Sunday morning before brunch with the family. And all of them need to be served immediately:
"The customer is waiting for a patch!"
"We need to release tomorrow!"
"This is blocking our business-critical process!"
Due to the their urgency, they forget to tell vital information such as what the blocking issue is, what files failed or in what workspace the problem occurred. I am very happy with my role as being the keeper to open a closed gate for you, but why is this done always so late in the game? Why isn't the gate pre-checked during the development phase? What do you think?
bert.ro
3wAll of the sudden, ALL nodes changed status from "ready" to "checking", while there is still no portal for potential customers, where tasks can actually be built. So what tasks are the nodes checking? I used the contact form a week ago to gain some insights on the actual gpu arhitecture behind, still no reply. How can a serious project use a contact form from an external provider for all action buttons on the website? Two possible outcomes here: the portal is still under development, or, there is no actual GPU arhitecture and the whole project is a scam. My bet is on option 2 atm, since you fail to reply or communicate in a transparent way.