@meekrosoft @perbu Not direct collab maybe, but as “executable documentation“ it helps alleviate the pitfalls of handovers. And automation and repeatability are also important for DevOps flow and fast feedback loops.
@taw_moto @meekrosoft Not really a problem on the MacBooks. I used to sticker mine up, and roughly every 2 years I found myself pealing them off, cleaning the lid and starting over. All told it’s just another non-destructive expression of personality and a great conversation starter.
I don’t see why developers make six figures, all they need to know is:
- Linux
- Bash
- Go
- Python
- JavaScript and frameworks
- Git
- Docker
- Kubernetes
- Terraform
- Distributed Systems
- AWS
- GCP
- Prometheus
- Grafana
- Being On-call
- Security
@RandomSort@Andrey9kin@SofusAlbertsen I agree with @RandomSort. The diff. git/text based tools look really nice for standard text presentations with images, but nothing really suitable for technical content with e.g. git graphs or network diagrams. Then you will just be searching for the next tool to manage those. 🤪
@Andrey9kin@RandomSort@SofusAlbertsen Co-editing is what the google docs suite is made for. The thing that becomes hard in a big slide deck is seeing what changed from version to version.
@nicolefv @jaredweakly @log1kal Please continue asking/expecting. Reactions like this may be (very) humiliating, but not finding out that a partner is “unsound” for you and staying in the relationship (for years maybe) is much more unhealthy for you! 🤕
300+ signups already. I had expected around 50-60 tops. 🤪😱
Luckily the fact that it will be in Danish somewhat limits it from growing totally out of proportion 😉
Why the need to *rely* on devs testing locally? I would go with automated pre-tested integration, and then (optional/on demand) review after integration, ideally synchronized team-review if possible.
Ancient sysadmin wisdom: don’t use ‘>’ as part of your shell prompt. You’re one copy/paste error away from truncating a file.
There’s a reason root’s ‘#’ prompt gets interpreted as a comment.
@QuinnyPig Way back before this behavior got built in to most rm’s:
I usually had a file literally called -i in my home dir. So rm * would shell expand to rm -i <other files...> and ask if I was sure.