-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathindex.xml
90 lines (90 loc) · 9.46 KB
/
index.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Notes of an awful developer</title>
<link>https://floriank.github.io/</link>
<description>Recent content on Notes of an awful developer</description>
<generator>Hugo</generator>
<language>en</language>
<copyright>(c) 2025 Florian Kraft</copyright>
<lastBuildDate>Fri, 03 May 2019 09:30:30 +0100</lastBuildDate>
<atom:link href="https://floriank.github.io/index.xml" rel="self" type="application/rss+xml" />
<item>
<title>Uploading files using Relay Modern and a GraphQL API made with Absinthe</title>
<link>https://floriank.github.io/post/uploading-files-relay-graphql-absinthe/</link>
<pubDate>Fri, 03 May 2019 09:30:30 +0100</pubDate>
<guid>https://floriank.github.io/post/uploading-files-relay-graphql-absinthe/</guid>
<description>Since I&rsquo;ve decided to finally give the TypeScript/React combo a spin, I have to admit that it&rsquo;s come quite far since I&rsquo;ve last tried it in 2016.
Making things overly complex I had decided to build a prototype for a friend - so naturally I thought of the most complex architecture and implementation and then threw it out immediately.
Taking what I&rsquo;ve learned, I decided to move the client application together with the backend and threw out the JSON API entirely.</description>
</item>
<item>
<title>Moving on from postgres_fdw</title>
<link>https://floriank.github.io/post/moving-on-from-postgres-fdw/</link>
<pubDate>Wed, 03 Apr 2019 09:30:30 +0100</pubDate>
<guid>https://floriank.github.io/post/moving-on-from-postgres-fdw/</guid>
<description>Revising the things you have done I sometimes go back and look at old code - it&rsquo;s a mostly cathartic, as it brings one back down to earth. As software developers we have a certain aptitude for documenting our code in tests (or actual self-documenting API specifications, e.g. using GraphQL), but we omit the power of documenting the decision making behind it.
I am no exception to this - which is why I look at old code like an interesting puzzle and try to reason with my past self about what he has been thinking during that time.</description>
</item>
<item>
<title>The steel industry, file_fdw and the synchronisation of data</title>
<link>https://floriank.github.io/post/the-steel-industry-file_fdw-and-postgres/</link>
<pubDate>Thu, 12 Jul 2018 09:30:30 +0100</pubDate>
<guid>https://floriank.github.io/post/the-steel-industry-file_fdw-and-postgres/</guid>
<description>Contents Steel me. On the process of selling metals world wide Synchronisation vs. Import PostgreSQL, how I love thee Foreign data wrappers file_fdw Using file_fdw with Ecto Transform the data The key to doing things fast Joining external and internal tables What to do next? Numbers, please! So, we use this all the time now? Learnings and a repository Steel me. My god.
It has been 2 years since I wrote something.</description>
</item>
<item>
<title>Using Phoenix with docker, Addendum: Exrm</title>
<link>https://floriank.github.io/post/using-phoenix-with-docker-addendum-exrm/</link>
<pubDate>Mon, 07 Mar 2016 12:28:34 +0100</pubDate>
<guid>https://floriank.github.io/post/using-phoenix-with-docker-addendum-exrm/</guid>
<description>This is an addendum to a three part series: Part 1 - Part 2 - Part 3
Contents Bad ideas Exrm Using Exrm with Kitteh Building the docker image(s) - once more. The agony with build environments Results! Assets Wait! Migrations! The problem with Mix.env So, we&rsquo;re going to ignore ImageMagick? Conclusion Bad ideas I have had some bad ideas in the past - building a container out of a Phoenix application like building it out of a Rails application wasn&rsquo;t probably the best idea ever.</description>
</item>
<item>
<title>Using Phoenix with docker, Part 3: Containerization</title>
<link>https://floriank.github.io/post/using-phoenix-with-docker-part-3-containerization/</link>
<pubDate>Mon, 15 Feb 2016 15:47:39 +0100</pubDate>
<guid>https://floriank.github.io/post/using-phoenix-with-docker-part-3-containerization/</guid>
<description>This is the final part of a three part series: Part 1 - Part 2 - Part 3
Note: I am using the latest docker-compose and the latest docker-engine later on in this post.
Contents Composition Kitteh Dockerfile Database connections Tearing it all down Container structure Creating the volume container Docker 1.10 Configuring nginx Running the containers Assets and images Looking back Cleaning up One more thing Conclusion So far, so good.</description>
</item>
<item>
<title>Using Phoenix with docker, Part 2: Implementation</title>
<link>https://floriank.github.io/post/using-phoenix-with-docker-part-2-implementation/</link>
<pubDate>Mon, 15 Feb 2016 15:32:22 +0100</pubDate>
<guid>https://floriank.github.io/post/using-phoenix-with-docker-part-2-implementation/</guid>
<description>This is part two of a three part series: Part 1 - Part 2 - Part 3
Contents Installation Elixir Phoenix Let&rsquo;s go Scaffolding Simpler times Providing a &ldquo;frontend&rdquo; New routes Reading the documentation Handle the file Shortcuts Resizing images GenServer Resizing Problems of the demo app Conclusion Installation Before we start, please make sure you install Elixir and Phoenix. If you do not care or have already installed both, you can skip the next section.</description>
</item>
<item>
<title>Using Phoenix with docker, Part 1: Introduction</title>
<link>https://floriank.github.io/post/using-phoenix-with-docker-part-1-introduction/</link>
<pubDate>Mon, 15 Feb 2016 12:21:24 +0100</pubDate>
<guid>https://floriank.github.io/post/using-phoenix-with-docker-part-1-introduction/</guid>
<description>This is part one of a three part series: Part 1 - Part 2 - Part 3
This part is an introduction to the project - consider skipping to part 2 if you do want some code
Contents Using Phoenix &amp; Elixir Using docker Project Kitteh Continuing A colleague of mine will not shut up about this.
Working at a company using Ruby for day to day work, Elixir seems pretty appealing.</description>
</item>
<item>
<title>Working around timing issues in docker compose</title>
<link>https://floriank.github.io/post/working-around-timing-issues-in-docker-compose/</link>
<pubDate>Thu, 04 Feb 2016 10:33:17 +0100</pubDate>
<guid>https://floriank.github.io/post/working-around-timing-issues-in-docker-compose/</guid>
<description>Containers I really like the concept of containers. Having been a somewhat avid vagrant user in the past, the speed gain that containers can provide over a virtual machine is a good sell to me. Also, having a very snapshottable environment I can bring up and down with dependencies packed neatly into containers is a plus. If you are reading this article you probably heard the sermon before.
If you did not hear the good word yet - read up on it.</description>
</item>
<item>
<title>About</title>
<link>https://floriank.github.io/about/</link>
<pubDate>Tue, 02 Feb 2016 15:56:42 +0100</pubDate>
<guid>https://floriank.github.io/about/</guid>
<description>I am a software developer. That&rsquo;s mostly it. I am not very good at it, but somehow I found my way into several companies and dealt with some larger projects, so I think I might have some experience. I currently work as a software developer / software architect at kloeckner.i and have built a team of about 25 developers there. We&rsquo;re tackling the challenge of transforming a whole industry and preparing it for a new digital age there - and I couldn&rsquo;t be happier to work with an awesome team of such gifted individuals.</description>
</item>
<item>
<title>Imprint</title>
<link>https://floriank.github.io/imprint/</link>
<pubDate>Tue, 02 Feb 2016 15:56:42 +0100</pubDate>
<guid>https://floriank.github.io/imprint/</guid>
<description>Angaben gemäß § 5 TMG required for compliance with German law
Es werden keine Daten meinerseits erhoben und keinerlei cookies oder ähnliches gesetzt.
Haftung für Inhalte Als Diensteanbieter sind wir gemäß § 7 Abs.1 TMG für eigene Inhalte auf diesen Seiten nach den allgemeinen Gesetzen verantwortlich. Nach §§ 8 bis 10 TMG sind wir als Diensteanbieter jedoch nicht verpflichtet, übermittelte oder gespeicherte fremde Informationen zu überwachen oder nach Umständen zu forschen, die auf eine rechtswidrige Tätigkeit hinweisen.</description>
</item>
<item>
<title>Introduction: First post</title>
<link>https://floriank.github.io/post/intro/</link>
<pubDate>Tue, 02 Feb 2016 00:00:00 +0000</pubDate>
<guid>https://floriank.github.io/post/intro/</guid>
<description>First post hype!
Erm. Not really. This is a first post to be made, but it contains nothing of interest really.
I always wanted a blog to share my world view and my opinion with a world that probably could not care less about both of them - considering the mass of blogs and opinions, tweets, Facebook pages, likes, upvotes, kitty videos, doge videos and similar currently in existence.
Nevertheless, I hope you can find something useful to you here in the future.</description>
</item>
</channel>
</rss>