profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/steffkes/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.

steffkes/absinthe 0

The GraphQL toolkit for Elixir

steffkes/absinthe_plug 0

Plug support for Absinthe, the GraphQL toolkit for Elixir

steffkes/amqp 0

Idiomatic Elixir client for RabbitMQ

steffkes/ansible-role-mysql 0

Ansible Role - MySQL

steffkes/apex 0

Awesome printing for Elixir

steffkes/ApiProblem 0

A PHP Exception to provide the functionality of the `application/api-problem` RFC proposal. This class creates simple JSON [RFC4627] and XML [W3C.REC-xml-20081126] document formats to suit the purpose described in [Problem Details](http://tools.ietf.org/html/draft-nottingham-http-problem).

steffkes/argo 0

Argo Workflows: Get stuff done with Kubernetes.

PullRequestReviewEvent

Pull request review commentpleo-io/analytical-engineer-challenge

Initial creation

 # analytical-engineer-challenge 🚀 The Pleo Analytical Engineer Challenge+++## Stewards: @team-poseidon+https://linear.app/pleo/project/stewards-analytical-engineer-challenge-192436dac756++## Welcome!+This repository houses the Pleo Analytical Engineer challenge. It contains a mix of detective work, ops-like work, programming and big-picture perspective. Your answer to the challenge will help us get to know you, and provide a fun context for subsequent discussion in our interviews :)++We hope you enjoy it!++## Introduction+We have created an imaginary scenario which we hope will allow you to show off your analytical engineering skills while also having some fun:++You've been tasked with taking over a small prototype for an ETL (Extract - Transform - Load) pipeline, meant to collate some data from several sources into a Data Product. The original author never finished the prototype, and they unfortunately also left very little documentation on how the prototype works! Part of this challenge is detective work, and so we've been intentionally vague in terms of describing how it works.++Luckily you're available to help investigate this, determine what needs doing, and fix it so that it becomes a functional prototype! ++## How to submit a solution++When you are done with the below challenge, you have 2 choices:++1. You can set it up as a private GitHub repository and invite the reviewers to the repository.+1. You can zip the solution up and send it by e-mail to the reviewers.++Please *do not* submit your challenge by creating it as a fork of the repository :)++## The Task++The ETL service (found in the `etl/` folder) is not yet implemented at all. This is your main task: create code which will fetch the data (as described below), assemble it into a table in the Postgres database, and display the results.+++- Remember that you are implementing the remaining parts of a _prototype_ -- you do not have to build something that is fully viable as a production-grade ETL system.++- The project contains a docker-compose based setup (see `docker-compose.yml`), which runs a service that is _not currently implemented_ and is meant to create the desired data set. It also spawns a PostgreSQL database that will act as our 'Data Warehouse' in this challenge, called `dwh` in the compose file.++- It should be clear how to run the project from this README. If you change things that would alter what is needed to run the project, remember to update this README file to ensure that the steps required to do so are up-to-date. If you leave the README unchanged, we will expect to be able to see your solution by simply running `./setup.sh`.++- You may improve and modify *any* part of the project, as long as the ETL service functions to acquire and assemble the desired data into the Data Warehouse.++- Please record your progress and thoughts on this task in the `PROGRESS.md` file, in whatever way you feel is appropriate, as you work on the task. We suggest a format similar to 'thinking aloud'. If you discover things that you think are poorly implemented in the existing code, and you don't want to fix them as part of the challenge, feel free to write there what you'd suggest doing / changing.++- We value well-written git commits at Pleo! Commits are our history that persists through both changing issue tracking systems and source code locations, and they help us understand _why_ something was done if we need to roll things back. If you have set up a private GitHub repository that you share with us, this is a good opportunity to show how you'd ideally write and size your commits.++### Hints:++1. The `etl` Dockerfile and `src` files shows signs that the original developer was not sure what tools to use+2. The `pgsql` command in the `etl` container appers to be already configured to connect to the Postgres database

appears?

TheBellman

comment created time in 3 days

Pull request review commentpleo-io/analytical-engineer-challenge

Initial creation

 # analytical-engineer-challenge 🚀 The Pleo Analytical Engineer Challenge+++## Stewards: @team-poseidon+https://linear.app/pleo/project/stewards-analytical-engineer-challenge-192436dac756++## Welcome!+This repository houses the Pleo Analytical Engineer challenge. It contains a mix of detective work, ops-like work, programming and big-picture perspective. Your answer to the challenge will help us get to know you, and provide a fun context for subsequent discussion in our interviews :)++We hope you enjoy it!++## Introduction+We have created an imaginary scenario which we hope will allow you to show off your analytical engineering skills while also having some fun:++You've been tasked with taking over a small prototype for an ETL (Extract - Transform - Load) pipeline, meant to collate some data from several sources into a Data Product. The original author never finished the prototype, and they unfortunately also left very little documentation on how the prototype works! Part of this challenge is detective work, and so we've been intentionally vague in terms of describing how it works.++Luckily you're available to help investigate this, determine what needs doing, and fix it so that it becomes a functional prototype! ++## How to submit a solution++When you are done with the below challenge, you have 2 choices:++1. You can set it up as a private GitHub repository and invite the reviewers to the repository.+1. You can zip the solution up and send it by e-mail to the reviewers.

and I think if we ever find someone who will explain he doesn't have an account on github ..

TheBellman

comment created time in 3 days

PullRequestReviewEvent

Pull request review commentpleo-io/analytical-engineer-challenge

Initial creation

 # analytical-engineer-challenge 🚀 The Pleo Analytical Engineer Challenge+++## Stewards: @team-poseidon+https://linear.app/pleo/project/stewards-analytical-engineer-challenge-192436dac756++## Welcome!+This repository houses the Pleo Analytical Engineer challenge. It contains a mix of detective work, ops-like work, programming and big-picture perspective. Your answer to the challenge will help us get to know you, and provide a fun context for subsequent discussion in our interviews :)++We hope you enjoy it!++## Introduction+We have created an imaginary scenario which we hope will allow you to show off your analytical engineering skills while also having some fun:++You've been tasked with taking over a small prototype for an ETL (Extract - Transform - Load) pipeline, meant to collate some data from several sources into a Data Product. The original author never finished the prototype, and they unfortunately also left very little documentation on how the prototype works! Part of this challenge is detective work, and so we've been intentionally vague in terms of describing how it works.++Luckily you're available to help investigate this, determine what needs doing, and fix it so that it becomes a functional prototype! ++## How to submit a solution++When you are done with the below challenge, you have 2 choices:++1. You can set it up as a private GitHub repository and invite the reviewers to the repository.+1. You can zip the solution up and send it by e-mail to the reviewers.

can we maybe skip this step? otherwise we're going to ask anyway for the access on the github repository because we're curious on the commits being made. I've never once looked at the zip archive

TheBellman

comment created time in 3 days

PullRequestReviewEvent

push eventsteffkes/freiraum-co.github.io

steffkes

commit sha c73e1999df4486f06b677d0b4cc5b119541e1013

add browser-sync package

view details

push time in 19 days

push eventsteffkes/freiraum-co.github.io

steffkes

commit sha 0b98e8f04d53810ba4ec1495926c398c4f7558a4

allow manual trigger

view details

push time in 19 days

push eventsteffkes/freiraum-co.github.io

steffkes

commit sha 3ba27b04bdea8e24b12fe98cd4ea40f984f5d892

try this workflow

view details

push time in 19 days

PR closed vuejs/vuepress

fix variable reference for frontmatter example

<!-- Please don't delete this template -->

<!-- PULL REQUEST TEMPLATE --> <!-- (Update "[ ]" to "[x]" to check a box) -->

Summary

What kind of change does this PR introduce? (check at least one)

  • [ ] Bugfix
  • [ ] Feature
  • [ ] Code style update
  • [ ] Refactor
  • [x] Docs
  • [ ] Build-related changes
  • [ ] Other, please describe:

If changing the UI of default theme, please provide the before/after screenshot:

Does this PR introduce a breaking change? (check one)

  • [ ] Yes
  • [ ] No

If yes, please describe the impact and migration path for existing applications:

The PR fulfills these requirements:

  • [ ] When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)

You have tested in the following browsers: (Providing a detailed version will be better.)

  • [ ] Chrome
  • [ ] Firefox
  • [ ] Safari
  • [ ] Edge
  • [ ] IE

If adding a new feature, the PR's description includes:

  • [ ] A convincing reason for adding this feature
  • [ ] Related documents have been updated
  • [ ] Related tests have been updated

To avoid wasting your time, it's best to open a feature request issue first and wait for approval before working on it.

Other information:

browsing across the documentation, I've realized that the sample is using a wrong reference. the variable is named lang in the leading frontmatter block - rather than language

+1 -1

1 comment

1 changed file

steffkes

pr closed time in 2 months

pull request commentvuejs/vuepress

fix variable reference for frontmatter example

This is a duplicate at least of #2821, which I came across only after opening this PR - sorry for that!

steffkes

comment created time in 2 months

PR opened vuejs/vuepress

fix variable reference for frontmatter example

<!-- Please don't delete this template -->

<!-- PULL REQUEST TEMPLATE --> <!-- (Update "[ ]" to "[x]" to check a box) -->

Summary

What kind of change does this PR introduce? (check at least one)

  • [ ] Bugfix
  • [ ] Feature
  • [ ] Code style update
  • [ ] Refactor
  • [x] Docs
  • [ ] Build-related changes
  • [ ] Other, please describe:

If changing the UI of default theme, please provide the before/after screenshot:

Does this PR introduce a breaking change? (check one)

  • [ ] Yes
  • [ ] No

If yes, please describe the impact and migration path for existing applications:

The PR fulfills these requirements:

  • [ ] When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)

You have tested in the following browsers: (Providing a detailed version will be better.)

  • [ ] Chrome
  • [ ] Firefox
  • [ ] Safari
  • [ ] Edge
  • [ ] IE

If adding a new feature, the PR's description includes:

  • [ ] A convincing reason for adding this feature
  • [ ] Related documents have been updated
  • [ ] Related tests have been updated

To avoid wasting your time, it's best to open a feature request issue first and wait for approval before working on it.

Other information:

browsing across the documentation, I've realized that the sample is using a wrong reference. the variable is named lang in the leading frontmatter block - rather than language

+1 -1

0 comment

1 changed file

pr created time in 2 months

push eventsteffkes/vuepress

steffkes

commit sha 0bdef0810a657d64ec11409ebacf822bca093893

fix variable reference it's named `lang` in the frontmatter, not `language`

view details

push time in 2 months

fork steffkes/vuepress

📝 Minimalistic Vue-powered static site generator

https://vuepress.vuejs.org

fork in 2 months

push eventsteffkes/muell

steffkes

commit sha f5d1cc08cd4f749270292029b43a69e4530e4a55

fix wrong filename

view details

steffkes

commit sha a581a2ce88570d2b1ea29f56aebc05e6558b613f

show events as full-day events

view details

push time in 2 months

PR opened pulumi/pulumi-hugo

fix github actions

while toying around with pulumi on github actions, I've copied & pasted the examples from the website and accidentally run prettier on them:

$ prettier .
.github/workflows/pulumi-deploy.yml
[error] .github/workflows/pulumi-deploy.yml: SyntaxError: All collection items must start at the same column (1:1)
[error] >  1 | name: Pulumi
[error]      | ^^^^^^^^^^^^
[error] >  2 |   push:
[error]      | ^^^^^^^
[error] >  3 |     branches:
[error]      | ^^^^^^^
[error] >  4 |       - master
[error]      | ^^^^^^^
[error] >  5 | jobs:
[error]      | ^^^^^^^

which made me wonder why, until I've realized the on: definition is missing from them

+4 -0

0 comment

1 changed file

pr created time in 2 months

push eventsteffkes/pulumi-hugo

steffkes

commit sha 73bd0a23958b57cff7cd589223542e6f75f5cec2

fix github actions

view details

push time in 2 months

fork steffkes/pulumi-hugo

A Hugo module containing the Pulumi Hugo theme and website content.

fork in 2 months

push eventsteffkes/moneypenny-public

steffkes

commit sha c59105863e4495ac2f585a8749537b6c1538a3c1

update data

view details

push time in 3 months

push eventsteffkes/moneypenny-public

steffkes

commit sha 8b94c448257d6c2b4fe34c5d42e5fa7d3795b6c4

update data

view details

push time in 3 months

push eventsteffkes/moneypenny-public

steffkes

commit sha 7b6d3e8e0cbacf788549f178d7b11ce385569df1

update data

view details

push time in 3 months