I’m interested in Apache Kafka Streams and would like share some information on this topic with you. There is a great talk about Stream Processing from Neha Narkhede who co-authored Apache Kafka and is currently a co-founder and Head of Engineering of Confluent.
Have you ever wondered how git works internally or why git does certain things in a certain way? Recently I found an interesting talk about git’s internals on goto; conference. It explains all the building blocks that you need to understand to better understand git.
Knowledge is Power: Getting out of Trouble by Understanding Git
But how many questions on each topic have to be answered in the exam? The total number of questions is 60 and the expected number of questions on each topic can easily be calculated:
Overview of exam questions per topic
Business Logic and Process Automation
Data Modeling and Management
My strategy is to begin with the most important topic with the most questions and work my way down to the end of the list.
This post is the beginning of a series of posts on how I prepared for the exam. This part gave an overview of the topics and their weights. In the next part of I will focus on “Business Logic and Process Automation” in Salesforce and go into more depth.
Since several months I work as a Full Stack Software Engineer for Scoop & Spoon, a creative digital & internet agency based in London (UK), Vienna and Graz (Austria). I was wondering which other digital & internet agencies are out there and luckily found an interesting article in the brand eins magazine regarding this topic. The following list is a compilation of interesting agencies out there:
As a developer, there comes the time were you think about how to version your software. One approach is “Semantic Versioning” which leverages the level of change on your public API. Depending on what you changed in your code, Semantic Versioning proposes different version numbers:
Given a version number MAJOR.MINOR.PATCH, increment the:
MAJOR version when you make incompatible API changes,
MINOR version when you add functionality in a backwards-compatible manner, and
PATCH version when you make backwards-compatible bug fixes.
Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.
Seems to be an appropriate scheme on versioning software. Which other schemes do you think about? Leave me a comment then I’m going to update this post accordingly.
“The country is enjoying something of an entrepreneurial renaissance, driven largely by the return of some highly successful founders whose presence has awoken its capital Vienna from a start-up winter sleep.” [by Forbes]
The Austrian startups that made it to the article are the following ones (details on the startups can be found in the article and on their corresponding website):
Although Austria offers quite some support for starting a business (e.g. by granting loans, issuing bank guarantees and R&D grants, availability of cloud services such as AWS and Google App Engine) it is still not as startup friendly as it should be. High labour costs, high payroll-taxes and high health insurance costs not to forget the lack of real tax incentives for startups and startup investors to give some examples.
Florian Dorfbauer, CEO and co-founder of Austrian website feedback startup Usersnap states:
“I expect that Vienna will be the number one start-up hub of Central and Eastern Europe (CEE) – other CEE capitals like Budapest or Bratislava are within a few hours’ travel time – and I expect the dogma ‘Move to Silicon Valley or Die’ to shift towards ‘move some people to Silicon Valley and keep the core-team in Austria’, as there is little reason to expose an early- to mid stage start-up to Silicon Valley cost structures.
“And of course I expect a string of successes from my fellow start-up colleagues, so yes, I am feeling very optimistic about Vienna.”
If this is the future of Austrian Startup Scene then I’m looking forward to it. What do you think about the Austrian Startup Scene? Leave me a comment or drop me a note on @hmuehlburger.
Do you think about starting your own company? Then you should think carefully about the elementary skills you need to do so. What are the eight elementary skills every entrepreneur needs? Thomas H. Byers et. al. compiled the following list in his book on “Technology Ventures – From Idea to Enterprise”:
Entrepreneurs initiate and operate a purposeful enterprise.
Entrepreneurs operate within the context and industrial environment at the time of initiation.
Entrepreneurs identify and screen timely opportunities.
Entrepreneurs accumulate and manage knowledge and technology.
Entrepreneurs mobilize resources (financial, physical, and human).
Entrepreneurs assess and mitigate uncertainty and risk associated within the initiation of the enterprise.
Entrepreneurs provide an innovative contribution or at least a contribution that encompasses novelty or originality.
Entrepreneurs enable and encourage a collaborative team of people who have the capabilities and knowledge necessary for success.
I encourage everyone to have a look at this great textbook. It contains a lot of useful information on starting your own enterprise.