DEV Community: Bernhard Webstudio

If Your Eyes Are Fooling You: Up-to-Date Content: Books vs. Websites

Bernhard Webstudio — Sat, 01 Sep 2018 13:00:43 +0000

Unlike books and newspapers, old websites can be updated in design so that content looks up to date again without it being! Sure, you can release a new edition of a book or reprint the newspaper. Still, I would say it is not comparable to the simplicity of doing that to a website, most importantly the distribution part. For anyone visiting the website it will have a fresh look; the book would have to be rebought, and who does that when you still have the old edition?

For certain applications, I am absolutely sure this is a wonderful thing that has to be embraced. For others, I can see some problems; outdated data, scientific results or best practices should be clearly distinguishable as such. Not sure how to cope with that; never forget to look at the date of a blog post?

It can certainly be used for evil, will be, is used for evil; additionally, asserting the date – if there is any – as an outstander is probably impossible.

Tell Your Story: Has your application been hacked?

Bernhard Webstudio — Fri, 23 Feb 2018 06:28:15 +0000

Tell Your Story: Has your application been hacked? If so, what was your mistake to let that happen, what did you learn from it, and what were the consequences?

How do you handle framework upgrades in teams?

Bernhard Webstudio — Wed, 27 Dec 2017 13:31:04 +0000

I tend to get headaches when having to plan an upgrade of a framework bringing breaking changes, quite possibly caused by a lack of trust in (my) git (skills). Fortunately, I mostly work alone on such projects, so I can easily just finish and merge all my feature branches, before upgrading the framework as the final step. Only then start again with new features.

But honestly, this can not be the way to go. This is why I want to ask you now, how do you handle this in teams? Suppose the following scenario:

upgrade
- necessary as soon as possible (security? mad boss?)
- brings breaking changes
  - file & directory structure
  - configuration
  - few deprecations dropped
team
- has open feature branches
  - changes to configuration
  - can not be merged before upgrade
- should obviously not upgrade each and everyone for himself

This may be a near-to-worst-case-scenario, but I wonder what is the git workflow to handle the upgrade and merge the feature branches later? Is this something that just works by default and I make me think for nothing?

Hi, it's me, Tim Bernhard from Bernhard Webstudio

Bernhard Webstudio — Sun, 25 Jun 2017 12:48:21 +0000

I have been coding for [big number] years.

You can find me on GitHub as BernhardWebstudio

I live in Switzerland.

I founded Bernhard Webstudio when I got 18. Since then, Bernhard Webstudio is my "Company-Identity", used to publish, distribute and sell my programming skills.

Nice to meet you.