I wanted to add a bit of value to the Internet as I spent quite some time researching Hex and Richard Heart.

FYI, updates on PulseChain.com and the Sacrifice Phase.
PulseChain infos:
* Proof of Stake with built in Stake delegation
* 4x throughput compared to ETH (3sec blocks instead of 12sec)
* Mirror of ETH (will be announced when the snapshot will take place)
* Token distribution by airdrop/mirroring

You send crypto to an address (that Richard Heart probably controls or may just be a black hole). Currently over 170Mil $ have been sacrificed + 22 Mil as donations…

Illustration of a bitcoin coin
Source: Forbes

I’ll condense a lot of hours of study into this article.

#defi #bitcoin #btc #tesla #future #eth #microstrategy #lastbullrun

Update! While writing this draft, it was announced that Tesla bought $1.5bil of BTC

ScaleIT uses a semver compatible versioning schema that includes the date of the modification release.

2.2018.05.1 - version 2 Monat 05 patch 1
2.2018.04.1 - version 2 Monat 04 patch 1
2.2018.04.0 - version 2 (major - breaking changes) Monat 04, erste Version (patch auf 0)
1.2018.04.13 - version 1 Jahr 2018, Monat 04, patch 13
0.2018.04.7 - beta version, development vor dem ersten release, patch 7 (kein Tag)

Minor version (datum) wird nur erhöht wenn das auch ein minor update ist (sprich Funktionsumfang vergrößert wird).

ScaleIT repository use a Master, Production and Dev branch combination, where Master and Production are protected branches.

  • Master is the merge branch for running code.
  • Production is the branch for production grade code, ready to be rolled out.
  • Dev should contain running code, but there may still be showstopper bugs present

Today I’m working with dotnet core and Docker. Microsoft is really doing a great job, but there are still a few nooks and crannies to be fixed.

So in order to spare you some frustration, here’s the tl;dr:

  • I’m using a dotnet new webapi project to do some static hosting and C# logic
  • I couldn’t get the alpine-runtime and runtime-deps working with a binary build (-r) due to some unresolved dependencies. It was due to the base image — maybe it’s already solved.
  • I am using FROM microsoft/dotnet:2.1-sdk AS build-env and FROM microsoft/dotnet:2.1-runtime-alpine AS deploy-env
  • microsoft/dotnet:2.1-sdk …

There are two methods:

  • Use the stack
  • Don’t use the stack

The HTML below shows the usage difference.

As you can see in the below typescript, we need to import and declare the page2 component in order for the `navPush` element to understand where it should link to.

For the simple HTML linking, you need to use Ionic DeepLinks (IonicModule->forRoot->links):

This article that helped me understand how pages and navigation work:

If you want to get started with Industry 4.0 App development, you can check out our platform and App Skeleton (Scaffolds/Archetypes) at github:

That is a huge spike in discussions and contributions after the project goes open source. Like the example of roslyn below.

Disclaimer: I literally just copy-pasted stuff from here: https://github.com/blog/2195-the-shape-of-open-source

Thanks Arfon Smith (https://github.com/arfon) for the nice article.

For projects with just one contributor, pushes (in red) represent the vast majority of all activity.[…] As the number of contributors increases however, the fraction of activity in conversational mediums increases rapidly.

An even more dramatic example of this can be seen in the activity around Roslyn, the .NET Compiler Platform which was made open source by Microsoft in 2014. You can see a steep uptick2 in activity as the project moved from closed to open source.

Fingers crossed I’m going to see this with the ScaleIT platform.

Die Digitalisierung der produzierenden Mittelständischen Industrie ist einer der wichtigsten Schritte der folgenden Jahre.

Durch Digitalisierung ist nicht nur die Anschaffung von Software zu verstehen, sondern:

  • Die Befähigung eigene Software zu schreiben
  • Fremde Software zu integrieren
  • Projekte in einer optimierten Art und Weise durchzuführen (Versionierung, Werkzeugunterstützung, digitale Kollaboration)
  • Herr über die eigene IT Landschaft im Unternehmen zu werden

Das ist meine peröhnliche Sicht auf Industrie 4.0. Hinter dem Buzz-Word verbirgt sich kurz gesagt die Steigerung der Software-Fähigkeiten eines Unternehmens (Kultur, Arbeitsweise, Output).

Es wird einen Wandel geben weg von hauptsächlich Hardware hin zu hauptsächlich Software und Diensten. …

Open Source is a mentality, if you by it live, you could also be doing closed source development and still benefit. Closed source after all is just open source inside your company.

Pillars of Open Source

Why german manufacturing? Because it is one of the most important contributor to the industrial output of the world. High innovation is the norm. However that is just regarding the physical products. Software still lags behind.

Enter Open Source and with it ScaleIT. We strive to provide the bedrock for

Manufacturing is still lagging behind in the software domain. With notable exceptions such as the Musk Empire, not many embrace the potential that a software-centered production has.

In my research I aim at upgrading not only the software stack of the companies but also their mental models. Mental models are just brain software and thus the loop closes.

The result I am hoping for is a 3–4 generation jump in architecture, mindset and used tools:

  • Yet another custom built monolith -> Buying monoliths -> Microservice Based ecosystem -> Serveless business support
  • Waterfall based approach to software -> Agile -> SCRUM…

Whatch this video!

Behold the Light Revolution in Romania #rezist

I wrote other articles doing my best to explain what is happening in Romania:

Andrei Miclaus

Software Architect, Industrial IoT, Cloud Native and Calisthenics Fan.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store