Hubspot/Jira/G Suite → (Python) → PostgreSQL → (SQL) → Tableau
Since we are Tableau partners, we have a bunch of internal licences either way. We host Tableau Server, ETL, and PostgreSQL ourselves, all on Centos cloud servers.
1,355 karma · joined February 17, 2012
Hubspot/Jira/G Suite → (Python) → PostgreSQL → (SQL) → Tableau
Since we are Tableau partners, we have a bunch of internal licences either way. We host Tableau Server, ETL, and PostgreSQL ourselves, all on Centos cloud servers.
Another issue for cyclists is the permanent danger of getting your wheels in the rails, which means you are likely to either come to a sudden stop or, worse, come off your bike. There were experiments with "self-sealing" tram tracks that would lessen these risks, but no real solution exists quite yet, as far as I am aware.
That said, it baffles me why I have to restart Tableau Server 3 or 4 times during installation, and why I have to restart it for trivial changes more generally. For a piece of software that specifically ships with a cluster controller and full-blown zookeeper, somehow their engineers (or "engineers", as I sometimes get the impression) manage to make things that should be trivially solvable with reloads, partial restarts or spawning new workers (e.g. SSL certificates for the built-in Apache webserver) require a complete restart of the whole node.
edit: Regarding Power BI -- I feel that Tableau Server is (for better or worse) one of the killer features for many enterprise customers, because it means all of your data can remain within your own infrastructure and does not have to rely on external cloud providers. If that is not a requirement in your organisation, Power BI might make sense depending on your overall IT landscape, as well as your users' specific needs. On the other hand, if your organisation requires hosting things yourself, I guess it doesn't matter how miserable the experience is for you as an administrator. That's basically Tableau Server in a nutshell.
Or Tableau can continue to pretend that this isn't a real issue and stonewall customers and partners alike.
I think the actual visualisation part is neat, and better than many competitors, but many of the server-side parts are various levels of disastrous (as is their support), and their "data preparation" tool needs some serious improvements to be borderline useable.
15+ billion seems like a lot to me given how Tableau interacts with customers and partners alike, especially seeing how they are activelly alienating existing enterprise customers, all in favour of new sales, but perhaps something will change for the better here.
https://fosdem.org/2019/schedule/event/cloud_is_another_sun/
I sometimes use the Package Management part of it, since searching for something is sometimes quite nice in it. That said, I don't use it for installing software or doing updates etc., so you can absolutely use e.g. zypper & YaST side-by-side.
Indeed, I think that RedHat & SuSe are very similar in their ideas and in their usage patterns. Both contribute quite a bit to upstream projects (there is a lot of work being done on CNCF-stuff in both places, both are RPM-based and both offer a number of different "tracks" depending on your needs). openSUSE also has been very good at keeping up with things that are in development.
On the desktop-side, I think openSUSE is actually nicer, since they officially support a myriad of DEs (notably both Gnome and KDE).
For what it's worth, I use (and have been) using openSUSE both on my work laptop and my private laptop as my daily driver, and I use openSUSE on various private projects as a server OS, though I'm using CentOS 7 at work for all our servers because some of the software we use only supports Ubuntu LTS and CentOS (because the vendor is incapable of building non-idiotic RPMs/DEBs...).
For RPM-based distros (e.g. openSUSE), you write a .spec-file, check it in via OBS's version control alongside your sources, and off you go. OBS builds the package (and pulls in dependencies as needed etc.) and publishes the result as a repository with GPG keys and all the jazz, which you can just add to your own distro, and which is openly visible, so everybody else can use your package(s), too.
OBS also supports forking existing packages, and you can merge them back together, which means you can fix something in an existing package (whether a distro-package or something somebody else put up) and if they accept the changes, congratulations, you just fixed something in the distribution.
This means a lot of building, compilation, versioning etc. is out in the open, and you always have the sources available on top of it.
As an aside: I doubt people will "flock" to openSUSE, since many people sneer at them for no good reason (YaST, still?!), but they do a lot of good work, are good upstream contributors (like RedHat and unlike Ubuntu) and some of the tooling is absolutely amazing, except that nobody really knows about it.
[0]: https://en.opensuse.org/Portal:Build_Service
[1]: https://fosdem.org/2019/schedule/event/distribution_build_de...
Podman also uses the same notion of pods, and it doesn't support docker-compose syntax/files, because RedHat strongly believes that Kubernetes has already won. Basically, podman/podlib allow you an easy migration path from your local computer to a k8s cluster, with the same images and same concepts. Have a look here: https://github.com/containers/buildah#buildah-and-podman-rel...
Since when is the UK "on the continent"?
https://8os.io/body-35c3-hackers-conference/
Essentially, this seems like it combines ideas from Tai Chi, Aikido, mindfulness and a bunch of other sources to reflect upon the automatisms we all necessarily develop and have developed.
It sounds a bit esoteric, but not more so than other martial arts, which also similarly suggest to help us develop insights that apply beyond the martial art itself.
~/Downloads/programs for OS images, large binary blobs etc.
~/Development/<technology>/<project name> for development projects
~/Documents/<project name/company name> for documents relating to specific projects or customers
~/Operations/<server> for various files related to servers and infrastructure (manual backups etc.)
/dev/shm as a dumping ground for temporary files that I would like to get rid of with a reboot
"Was quasseln denn die Krittler\\vom bayerischen "Schorf"?\\ Hier gibt es keinen Hitler\\und keinen Ludendorff.
Was unken denn die Käuze\\vom Monarchistenputsch?\\Kein Mensch malt Hakenkreuze.\\Was futsch ist, gilt für futsch.
Ihr hört die Konstatierung\\nur zweifelnden Gesich's?\\So fragt halt die Regierung:\\die weiß von allem nichts.
Fragt nur den Herrn von Knilling,\\der wiederum Minist-\\er und sein eigner Zwilling\\von anno achtzehn ist."
(cf. Ratatöskr: Zur Beruhigung, in: Simplicissimus, vol. 27, München: Simplicissimus-Verlag, 1922--1923, p. 500)
Racket has a minor language for shell mix-ins[1] and Racket itself has some nice ways of dealing with command-line arguments[2]. However, all command-line arguments are passed as strings, which means extra steps in converting them to native types (numbers etc.). I find it very pleasant and Racket in particular has both a good standard library and a whole bunch of libraries that probably cover a majority of what one might need for smaller tasks. But again, it depends on what you consider "small-scale programming"
[1]: http://docs.racket-lang.org/rash/index.html
[2]: http://docs.racket-lang.org/reference/Command-Line_Parsing.h...
This might very well be the slightly awkward clash between a generally anglophone audience and their regular focus on the US and, to a lesser degree, England, combined with the spectre of "evil" Marxism.
When it comes to "huddling", Heidegger's "Sein & Zeit" (Being & Time) at the very latest emphasised the importance of being-in-the-world and being-with-others, rendering being entirely social (and this is despite the fact that the book remained, in essence, a fragment). Similarly, Wittgenstein's "Philosophischen Untersuchungen" (Philosophical Investigations) also highlights the shared nature of language games and the importance of society when he ponders the overall possibility whether private language(s) can exist. In doing so, both remain thoroughly wed to the modern world and do not harken back to a "simple society" or some such.
However, this list seems to suggest a different bias by describing the Western World chiefly as one designed by Smith & Hobbes, leaning on a relatively narrowly defined notion of anglophone philosophy to define the status quo as a direct consequence of the Enlightenment. It also betrays a fairly narrow focus on the US, since, as one comment on the site itself rightfully asks, this fails to account for developments such as the modern welfare state in various places outside the US, which would have to be impossible for a strictly isolated and/or egoistic society that forgot the importance of living together. And while the review off-handendly discounts both capitalism and communism, it fails to account for any of the real-world examples of societies located somewhere between these two polar opposites, as these social contracts seem to fulfil exactly the kind of "moral economy" that seems to be at play. That said,because these countries, in turn, face their own turmoil and challenges, this would seemingly get us back to where we started, except that we would already have gotten rid of an overly simplistic dichotomy that seems to have Smith and Lenin as their respective strawmen-come-cornerstone. In that case, however, we're faced with an interesting conundrum: If neither capitalism nor communism is the right answer, and if seemingly moderated in-between states face similar challenges, what exactly does the book advocate that is not yet another utopia that somehow safeguards the individual's freedom while also including it in a network of social interaction, responsibility and mutual assistance without being like any of the discounted examples or extremes?