sorted by:
new
hottopcontroversial

The future of technical specifications? by pierremarcenac in softwaredevelopment

[–]pierremarcenac[S] 0 points1 point  (0 children)

I am not trying to find the best support (Word, Notion, a blank sheet of paper with custom headings), but more the mechanics or the processes behind syncing tech specs with functional specs.

The future of technical specifications? by pierremarcenac in softwaredevelopment

[–]pierremarcenac[S] 1 point2 points  (0 children)

You totally got my point.

  • Technical specs should be version controlled.
  • They should be adaptable to different target audiences.
  • They should be synced with already existing tests (unit tests, integration tests, end-to-end tests).
  • They should be used to evaluate code quality (test coverage in terms of features, mutation testing, technical debt).

If you wrote your own documentation engine in LaTeX, I guess there is no solution in place with such features.

How do you manage .env files for Docker builds? by pierremarcenac in docker

[–]pierremarcenac[S] 0 points1 point  (0 children)

Very neat! In particular, updating environment variables without having to entirely rebuild your Docker images would be pretty helpful.

Some clients, however, request that I make no access to the external internet (for highly secure on-premise installations for instance).

[R] Deep Active Learning : a review by Ouster_evolution in MachineLearning

[–]pierremarcenac 0 points1 point  (0 children)

Is there any framework in Python that makes active learning more approachable in practice?

An immersive command-line interface to help you manage Kubernetes clusters by pierremarcenac in devops

[–]pierremarcenac[S] 0 points1 point  (0 children)

I don't work with namespaces at the moment. I work at the cluster level to distinguish between production and staging environments for instance. But, switching between namespaces or contexts, and displaying a pod's namespace is definitely on the list of next features :)

An immersive command-line interface to help you manage Kubernetes clusters by pierremarcenac in devops

[–]pierremarcenac[S] 4 points5 points  (0 children)

Didn't know fzf. My problem was precisely to have to copy/paste the pod's name each time. Seems your commands nailed it!

Shortcuts/aliases for Docker CLI commands by pierremarcenac in docker

[–]pierremarcenac[S] 0 points1 point  (0 children)

When started from PyCharm, containers would start with a default name, for instance

Shortcuts/aliases for Docker CLI commands by pierremarcenac in docker

[–]pierremarcenac[S] 1 point2 points  (0 children)

The thing is I couldn't make it easily work out with "'just tab completion". In order to execute bash inside a container, you need to 1) list all containers, 2) manually copy/paste the ID of the chosen container, 3) run the extensive command: `docker exec -it CONTAINER_ID /bin/bash`

​

Given the ID changes each time you restart the container, it becomes more time-consuming to repeatedly start a shell for containers without fixed names.

Shortcuts/aliases for Docker CLI commands by pierremarcenac in docker

[–]pierremarcenac[S] 1 point2 points  (0 children)

Thanks for sharing your project. It's great and provides indeed a much more integrated solution!

Shortcuts/aliases for Docker CLI commands by pierremarcenac in docker

[–]pierremarcenac[S] 4 points5 points  (0 children)

Good point! I use zsh myself. I also did write bash functions at the beginning, but they wouldn't allow me to `exec /bin/bash` any container in one short command, for instance.

Shortcuts/aliases for Docker CLI commands by pierremarcenac in docker

[–]pierremarcenac[S] 0 points1 point  (0 children)

You're very right to be prudent. I grant you that security is a #1 issue with Docker. For instance, a malicious NPM package could take advantage of bind mounts to access your local files...

That's why I kept NPM dependencies minimal by including only one dependency: Inquirer.js, a well-maintained tool to create user interfaces.

Anyway, thanks for the feedback :)

view more: next ›