axd1967

This is an interesting discussion.

I believe that this attitude of avoiding acronyms tells something about people that are whining, sorry. They have something in common: they are new on a project, or never bothered looking up an acronym or have no time or no energy to do so, or are still struggling with the acronym (I have never mastered an acronym of one project I worked in for in years, namely SASS-C, I do understand the issue, but this has never stopped anyone I know from working). I think it is the irritation of not knowing what is being talked about, not being in the loop, that gives acronyms a hard time. If you knew, you would not trip over the acronym.

Good luck with spelling out all those names. And making exceptions for acronyms that originate from outside the company? So you will torture your employees because you can't stay up-to-date with the new acronyms, but they will be allowed to use external acronyms? I think there is a different problem here.

Good luck with looking for names, then. The p

axd1967

#!/usr/bin/env python
"""
getimg.py

Gets the current image of the day from NASA and sets it as the
background in Gnome. The summary / description text is written
to the image.

Requires:
    PIL             (apt-get install python-imaging or pip install PIL)

axd1967

Urgent.fm livestudio handleiding

inhoud

1. Routing diagram
2. Afspraken
3. Livesessie workflow
4. Gebruik Midas M32 console
5. Gebruik Powerplay P16 (monitor mixertjes)
6. Materiaallijst

#1. routing diagram

axd1967

library(shiny)
library(shinyjs)


# used at https://ipub.com/shiny-crud-app/

# Get table metadata. For now, just the fields
# Further development: also define field types
# and create inputs generically
GetTableMetadata <- function() {