Skip to content

Commit 310562b

Browse files
bernedombernedom
committed
Fix wrongly placed author tag
1 parent 50475f2 commit 310562b

File tree

56 files changed

+124
-249
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

56 files changed

+124
-249
lines changed

‎_posts/2015-11-24-Get-Professional.md‎

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,10 @@
1-
---
2-
author: Dominik
1+
---
32
layout: post
43
title: Get Professional - A professional skillset for software developers
54
image: /images/get-professional/thumbnail.png
65
hero_image: /images/get-professional/thumbnail.png
76
hero_darken: true
8-
---
9-
author: Dominik
7+
---
108

119

1210
**Everybody is a great coder!** It's now over fifteen years since I first got money for a program that I wrote, and since over ten years I consider myself a professional software engineer. When I started out programming I was convinced that raw coding ability and deep, innate technical knowledge of a few programming languages would be all it would take to make it in the industry. But over the years I learned that there is more to being a professional programmer than hacking together complex code. Having worked both in academics and industry, this often became most apparent to me when working with newbies fresh out of college. Often they are great programmers, but lack some of the surrounding skills to make them look professional to me. So what distinguishes the common coder and/or hobbyist from the pros? Before I forget: This article is written on a purely subjective basis of my personal experiences, feel free to tell me that I'm wrong

‎_posts/2015-12-07-Reading-Educates.md‎

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,9 @@
1-
---
2-
author: Dominik
1+
---
32
layout: post
43
hero_image: /images/default-hero.jpg
54
hero_darken: true
65
title: The Seven Must Reads For The Aspiring Agilist
7-
---
8-
author: Dominik
6+
---
97

108
Over the course of the last few years I read a lot of books about agile principles and teamwork and there are some that stood out to me as particularly worth to read. Most of the books are rather about agile teamwork in general than any particular methodology such as scrum or kanban. These books are also starting point on the way to knowing and doing agile, so the list is obviously by no means complete.
119

‎_posts/2016-10-10-Efficient-Meetings.md‎

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,10 @@
1-
---
2-
author: Dominik
1+
---
32
layout: post
43
title: Five and a half steps to efficient meetings
54
image: /images/efficient-meetings/meeting-types-thumbnail.jpg
65
hero_image: /images/efficient-meetings/meeting-types-thumbnail.jpg
76
hero_darken: true
8-
---
9-
author: Dominik
7+
---
108

119
**Meetings are boring, overcrowded, take up much of your valuable time and don't produce the desired results.** Or they can be interactive, efficient, goal-driven, interesting and sometimes even fun. So how to go about planning and running successful meetings?
1210
Five and a half Steps to successful meetings

‎_posts/2017-11-10-Agile-Roadmapping.md‎

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,11 @@
1-
---
2-
author: Dominik
1+
---
32
layout: post
43
title: Planning ahead the agile way
54
image: /images/agile-roadmapping/thumbnail.jpg
65
hero_image: /images/agile-roadmapping/thumbnail.jpg
76
hero_darken: true
87
tags: agile software-delivery product-management
9-
---
10-
author: Dominik
8+
---
119

1210
**Agile is shortsighted! In scrum you are only interested in what's going on in the next sprint! Kanban focusses only on what's next! Long term planning is not agile!** Sounds familiar? The gap between short term (sprint-)planning and long term roadmaps is an often discussed focus point in the world of agile and an often cited reason why *"our company cannot do agile"*.
1311
And it is true. A lot of litarature advertises mainly the fast reaction time and short iteration cycles that agile methods give us, especially if applied to software development. But it is also true, that a lot of businesses are operating on longer cycles than single sprints. Yearly budget allocations, fixed cost projects and hard deadlines are real and existing challenges in the industry. Leaving aside if this is how it should be or not, those practices are still alive and kicking in a lot of industrial sectors such as the medical or machine industry.

‎_posts/2017-12-12-C++17-whats-in-it.md‎

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,11 @@
1-
---
2-
author: Dominik
1+
---
32
layout: post
43
title: C++17 - What's in it?
54
image: /images/cpp_logo.png
65
hero_image: /images/cpp_logo.png
76
hero_darken: true
87
tags: cpp
9-
---
10-
author: Dominik
8+
---
119

1210
**C++17 - is officially out!** So what can we as coders expect from it? With C++17 the standard-comitee brought further modernisation into the language. C++17 brings a set of new features which enhances convenience for the coder and makes writing portable code easier.
1311

‎_posts/2018-01-29-Stop-Calling-It-Agile.md‎

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,11 @@
1-
---
2-
author: Dominik
1+
---
32
layout: post
43
title: Stop calling it agile
54
image: /images/no-more-agile/stop-agile-thumb.jpg
65
hero_image: /images/no-more-agile/stop-agile-thumb.jpg
76
hero_darken: true
87
tags: agile
9-
---
10-
author: Dominik
8+
---
119

1210
**We should stop calling it *agile* and start calling it *modern company culture*.** In the past fifteen years the word 'agile' has become widely popular in software development and other technology affine areas of business, but still people find it hard to find a consensus on what 'agile' means for them or their company. There seems to be an agreement that agile development contains such processes as [scrum](https://www.scrum.org/), [kanban](https://en.wikipedia.org/wiki/Kanban), [xp](http://www.extremeprogramming.org/) or on a bigger scale [SAFe](http://www.scaledagileframework.com/), [Less](https://less.works/) or any of the other frameworks out there. But an often heard complaint by people involved in software development is, that they are never "100% agile". Or that they do scrum but find it hard to get that elusive *culture shift* happening in their companies.
1311

‎_posts/2018-02-05-selection_statements-with-initializers.md‎

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,11 @@
1-
---
2-
author: Dominik
1+
---
32
layout: post
43
title: initializers in selection statements - smarter coding in C++17
54
image: /images/cpp_logo.png
65
hero_image: /images/cpp_logo.png
76
hero_darken: true
87
tags: cpp
9-
---
10-
author: Dominik
8+
---
119

1210
**C++ is hard!** Luckily the new standards brought some features and tools to make writing C++ easier. Selection statements with initializers are one of these small-but-nice features that make our coding-life easier.
1311

‎_posts/2018-03-09-standard_attributes.md‎

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,11 @@
1-
---
2-
author: Dominik
1+
---
32
layout: post
43
title: Standard Attributes - CleanCode for C++17
54
image: /images/cpp_logo.png
65
hero_image: /images/cpp_logo.png
76
hero_darken: true
87
tags: cpp
9-
---
10-
author: Dominik
8+
---
119

1210
**Good code is self-documenting** - We coders love this sentence and with the standard attributes available since C++11 we are one step closer to this utopia.
1311

‎_posts/2018-03-20-Doing-Innovation.md‎

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,11 @@
1-
---
2-
author: Dominik
1+
---
32
layout: post
43
title: Do not leave your innovation to the engineers
54
image: /images/innovation/innovation_by_people.jpg
65
hero_image: /images/innovation/innovation_by_people.jpg
76
hero_darken: true
87
tags: agile innovation business
9-
---
10-
author: Dominik
8+
---
119

1210
**We need to be innovative!** - I heard this statement or a variation of it a few times over my past in working as a software engineer. We engineers love this, as we get more time to tinker with anything we find interesting - Which is a lot. The result are often better tools or tool-chains to make our life as developers easier, but **very rarely the output of such initiatives improves something tangible for the users of the product we are working on**. Why? Because on these innovation days we are usually stuck together with other engineers which means that we mainly discuss engineering problems.
1311

‎_posts/2018-04-01-linguistic-estimation-aprils-fools.md‎

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,11 @@
1-
---
2-
author: Dominik
1+
---
32
layout: post
43
title: Better estimates by using applied linguistics
54
image: /images/aprils-fool/aprils-fool.jpg
65
hero_image: /images/aprils-fool/aprils-fool.jpg
76
hero_darken: true
87
tags: april-fools agile
9-
---
10-
author: Dominik
8+
---
119

1210
**Planning poker, magic estimation, T-shirt-size estimation and even the famed \#NoEstiamtes are too inaccurate** - But there is a way to estimate to up to 50% more accurately by using a simple formula based on empirical measures and applied linguistics. Notice how developers use the same qualifiers for estimating workload over and over again? "It is just a minor bugfix", "This is a huge, complex task", "There is absolutely no way I can put an estimate on this one". Heard this sentences or variations of it in the past? Your best estimations are lying in front of you in plain sight.
1311

0 commit comments

Comments
 (0)