You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _tabs/about.md
+6-6Lines changed: 6 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ I am Thomas and currently occupied as an (Azure) data engineer at [Capgemini Aus
15
15
Not very surprisingly, my main focus is on all things data. More specifically, that currently means:
16
16
17
17
- Databricks, Spark & Delta
18
-
- Delta Live Tables & Spark Structured Streaming
18
+
- Delta Live Tables, Spark Structured Streaming, Eventhubs & Kafka
19
19
- Data Explorer/Kusto
20
20
- Fabric
21
21
- Azure Data Factory
@@ -27,31 +27,31 @@ And not so currently, meaning in the recent past, i saw a lot of:
27
27
- SQL-Server Warehouse(s)
28
28
- Restful APIs & GraphQL
29
29
30
-
After 18 years of classical data warehousing, i finally got to dive into the data lake (-house), which i won't leave anytime soon it seems.
30
+
After 18 years of classical data warehousing, i finally got to dive into the data lake (-house), which i won't leave anytime soon.
31
31
32
32
Besides signing the [DataOps Manifesto](https://dataopsmanifesto.org/), i am also a supporter of the "treat data as a product" movement.
33
33
34
34
## Side-Shows
35
35
36
36
Since one of my main treats is laziness (when it comes to repetitive tasks), i developed a natural interest in DevOps & automation. And due to constant lack of sleep, I usually don't touch any code, unless it's version controlled. That includes but is not limited to: cloud infrastructure (as code), database schemas, pipeline definitions, all kinds of scripts, notebooks and the grocery list for my next shopping tour.
37
37
38
-
As a result of the above, i somehow stumbled into the beautiful world of DevOps (although that name was not a thing back then). My personal project lifecycle these days often goes looks like this: Getting hired as an architect/data enginner at first, but then silently turning into the dedicated DevOps and Git guy. Although it was never my intention, i think i got the DevOps bingo card full now:
38
+
As a result of the above, i somehow stumbled into the beautiful world of DevOps (although that name was not a thing back then). My personal project lifecycle these days often looks like this: Getting hired as an architect/data enginner at first, but then silently tarnsitioning into the dedicated DevOps and Git guy. My DevOps bingo card includes:
39
39
40
40
- Azure DevOps (Repos, Boards, Pipelines, etc.)
41
41
- The Atlassian(s): Bitbucket, Jira, Confluence (and even Bamboo...).
42
42
- Github (my teenage love)
43
43
- Gitlab
44
-
- And if artefact registries also belong on this list: Cloudsmith
44
+
- And if artefact registries also belong here: Cloudsmith
45
45
46
46
However, there can be only one god. And for me that is and always will be: __Git__[^git]. After using it for almost a decade, i still feel like i don't know half of it and am constantly amazed how limitless the possibilities of this genius piece of software really are.
47
47
48
48
## Scripting
49
49
50
50
Since __DevOps and automation__ usually require some sort of scripting, i found myself dealing with the usual (scripting) suspects: Powershell, Bash, Python (and for fun and good looks also: Fish).
51
51
52
-
Regarding __data manipulation & transformation__ i am most experienced in T-SQL, due to spending many years implementing SQL warehouses. Switching to Python felt a bit odd at first, but today there is no doubt it in my mind: The added value one gets (for free) from the whole Python software engineering eco-system (formatting, linting, automated testing, packaging, ...) cannot be missed out on. Implementing data projects in Python almost starts to feel like 'real' software development these days.
52
+
Regarding __data manipulation & transformation__ i am most experienced in T-SQL, due to spending many years implementing SQL-Server warehouses. Switching to Python felt a bit odd at first, but today there is no doubt it in my mind: The added value one gets (for free) from the whole Python software engineering eco-system (formatting, linting, automated testing, packaging, ...) cannot be missed out on. Implementing data projects in Python almost starts to feel like 'real' software development these days.
53
53
54
-
Also, a life without (Jupyter) notebooks might be possible, but makes absolutely no sense to me anymore :smirk:.
54
+
Also, a life without (Jupyter) notebooks might be possible, but makes absolutely no sense to me anymore :smirk:
0 commit comments