341 karma · joined November 11, 2019
Analyzing the requirements is a hard problem when we do it with our brain. But our job would be very different if all we had to do it to write down the constraints, and press a button to see an error: invalid requirements, can't support this and that at the same time.
Is there such a thing as design continuity? or granular design change?
I guess the constructs of the programing language has to be designed to produce a visual representation: a strict hierarchy must be imposed to hide complexity.
At the end of the day, the question is: why using visualization? - if this is to use visual memory, can one trick the brain with colors, fonts and background images? - if this is to have 10,000 feet pictures, can statistics answer your questions?
Yes, and the same can be said from Chinese state media...
One must erase any reference to an historical fact in a matter of hours.
The other need to dismentle a network of criminals.
This is untrue. China (to survive as a dictatorship) may need to suppress any content. Without respect for laws.
Most country i have been to don't have this need. They need their law to be followed and use different means.
How strange it is to read such normalizing comment.
I also have a journal but it is not meant to be reviewed.
- ability to extract all memory component to reflash them
- pinctrl connectors for i2c/spi
- reboot of grey bus
- sdr components
Please make something incomparable!
In driver development I often see abstraction violations or very loose abstractions: news hw capabilities can't be accounted for when designing framework abstractions.
I have never done dev on windows, but I guess there is a reason why the form factor of things running windows is pretty limited. I don't see how you can have fixed interfaces in an ever evolving wold.
1. We sucks at hiring, so we need to train juniors on how to hire early. 2. Programs live in the head of their creators. The code is just a draft left for computer to execute. Build a human culture where the aspiration is discussed. 3. We don’t replace people, we hand over the responsibility. Be ready to work differently. 4. I conduct interview by asking the candidates to explain me I piece of work she is is proud of. If I understand the what, how and why, she usually pass. 5. Remember: most issues are not technical but organizational. We can train people, but we can’t change them. 6. Set high quality standards for your team. Make them proud of their work. On boarding will be easier.
So, it is less about how to hire the shinning star and more about how to welcome and how to create a culture around your values.
My two cents.