I really got a lot of use out of taking the GCP data engineer course on coursera (the one by google aimed at the cloud cert) and then later taking the actual certification.
With that being said it was very focused on BigQuery, and my impression is that it is that all their certs are now basically different variations of a kubernetes certification.
I used the Coursera course as well and yea, it's pretty good, so long as you do the labs.
To be fair though, BQ is the swiss army knife of GCP data engineering. I was a GCP DE consultant for many years and so much of the pipelines I put together amounted to, shove data into BQ as early as possible, then leverage SQL for transformations. Plus, most Google products have native BQ support (ads, GA, Youtube, etc), which makes it a must-have tool for a lot of companies.
This reminded me of a recent experience on WeChat. I hadn't used it for a few years and recently tried to log in.
I was told, that my account had been deactivate due to inactivity and that it was against my agreement with Tencent not to use WeChat regularly. After that I had to check a checkbox promising to log in regularly.
Luckily I haven't paid for WeChat, and I don't need it anymore to keep in contact with friends, so I was far enough removed from the situation to laugh at it.
To be fair, there is a known problem of social media / messaging accounts being hacked and reanimated by botters / scammers long after the actual account owners have stopped using them.
You really need 3 for the first puzzle and 1 for the second puzzle.
Spoilers ahead:
- 1st query to get the crime report. This contain plaintext clues.
- 2nd query to get witness interviews. Again, these contain plaintext clues that can't be used in a `join` statement or a `where` statement in SQL.
- 3rd query to get interview with suspect. This contain plaintext information needed for solving the second puzzle
- 4th query for finding the master mind.
Short of writing regexes that basically extracts the clues by looking for patterns that are verbatim the clues themselves, I don't see how it can be done any shorter than this.
I took a hint from Gorkish, having never heard of SQL triggers before, and I gotta say, the 2-query answer is really thinking out of the box and very clever. I learned a lot from it!
When doing my master thesis, I wanted my plots to be printable on a black and white printer in case my professor would print or photocopy it (you never know)
I wrote up a blogpost about my findings on how to generate monochrome plots. I haven’t really used matplotlibs since my thesis days, but it’s kinda funny to see what my thoughts back then were on the interface.
I found the OO interface a necessary evil and that you have to mix interfaces to get full control of your plots.
Maybe things have been ironed out in the past 5 years? Reading the comments here it seems like the sentiment is that the OO interface is considered the sane, true interface.
Mine is “first name at last name dot dk, only last name is spelled with an ‘O’ instead of an ‘Ø’” ...
It’s quite common when giving my email over the phone that my full name has already been established so I really wished the “Ø”-version would work (I also own that domain) but most (many? Some? Too many) email clients refuse to send emails to servers that contains special characters.
I can receive emails at the ø-domain, but not send to it using Fastmail. They recommend I use puny codes but that’s way too difficult to communicate.
> Why do most Danes use Ø or Æ in their names, but not Å?
I think because Å was added later than Ø or Æ (introduced in 1948 vs 1100 for the other two). People are hesitant to change the spelling of their names, so the old form "Aa" is still common in names like Aamand and Aagesen.
Same here, first at last dot country. But I'm unlucky to have a 15 character last name. Luckily in many cases whoever I'm telling my email to has my last name somewhere on their screen :-) if not things typically go wrong...
The zsh docs are good for the zsh specific expansions, but more man page than cheatsheet, though they do have an intro doc on it that's more cheatsheet like but less complete.
Also strips the path and you have to know the extension name(s). For my examples, "cut" would be appropriate. But those substitutions tend to work in anything POSIX, not just bash/zsh.
A lot of the tips from TFA can be done in BASH as well and I'm sure the following of my own zsh tips also have a bash equivelant, but I'd like to share anyway:
Pure theme - My absolute favorite shell theme. Has almost all the bells and whistles of the powerlevel9k shown in the article, but looks, much cleaner and less in-your-face.
After downloading the theme, I've added this to my `.zshrc` file:
# PURE theme - see https://github.com/sindresorhus/pure
fpath+=$HOME/.zsh/pure
autoload -U promptinit; promptinit
prompt pure
Fuzzy find makes searching history much more powerful than what is listed in the article. I only use it together with ctr-r, but you can set it up for even more goodness.
Inspired by similar plaintext to-do discussions on HN I also built my own system.
I use Sublime and I love scrolling. The second makes the system in TFTA not good for me, and given the first, I didn't mind my implementation being editor specific - but the principal is dead simple, as to not really matter.
I have a small custom function stored in Sublimes user package folder which, when called using the [cmd]+[shift]+p command palette will insert a small template in the top of the current file (my `daily.txt`).
This is just a headline with the date, and name of day of week and
Two lines called start and end (with datetime filled in in start) let's me keep loose track of my hours.
I also have a sub-heading that says to-do, with two `[ ] ...` txt checkboxes already added, another headline called did and a line that separates it from the previous day.
"To-do" is for things I plan on doing, "did" is for ad-hoc things I ended up doing. This helps me keep track of how much work I actually did, which is nice for days where everything is meetings and firefighting and I don't close issues in the tracker or PRs in git.
I can use go-to symbol to jump to a date, or just search the document for key words. Like I said, I like scrolling, and enjoy being able to just scroll down to see the previous day.
The system is like I said dead simple, easy to operate, easy for anyone to implement and customize to their liking. I've used mine for a few months and it has been great!
With that being said it was very focused on BigQuery, and my impression is that it is that all their certs are now basically different variations of a kubernetes certification.