Herbert Röblreiter / IT freelancer
I step in.
And get things done.
I'm an IT freelancer who gets up to speed and takes ownership of the next steps. I improve existing software, connect systems, and troubleshoot day-to-day operations.
01 / Where I help
Things get stuck.
I step in.
When does it make sense to bring me in? When outstanding issues remain unresolved, experience is needed at short notice or an environment needs to be taken over.
Choose what needs doing.
Where I step in
The unfinished work
needs someone.
A task is left unfinished. Decisions are missing and a change is only half complete. I learn the existing setup and take on the next practical steps.
- I start with
- What is already there: code, data and unanswered questions.
- To move things forward
- A manageable task that I take through to a testable result.
Where I step in
The data needs
a shared path.
Two systems hold the same information differently. I clarify which system is responsible for which data and develop the path between them. Errors must remain visible.
- I start with
- Data, identifiers and the actual processes.
- To move things forward
- A traceable data flow with clear responsibilities.
Where I step in
Make a change.
Keep working.
An application needs to move or an existing solution is being extended. I examine the dependencies and prepare the change so we can check it and roll it back if necessary.
- I start with
- The processes that need to remain available during the change.
- To move things forward
- A prepared transition with checks and a rollback.
Where I step in
The contact person is gone.
The systems remain.
The previous administrator or service provider is no longer available. I inventory the setup, clarify access and record what operations require. We agree on the tasks and responsibilities I take on.
- I start with
- Systems, services, backups and existing knowledge.
- To move things forward
- An organized starting point with priorities and clear responsibilities.
02 / Beyond the interface
The error message
is just the beginning.
An application is slow. I follow the path of a request until the cause becomes clear.
Follow along. Choose a point in the process.
In focus: the triggering process.
What I check at this point
What triggers
the process?
Does the delay occur on every request or only with certain inputs? I start with the specific process and compare the cases.
- The question
- Can the delay be reproduced?
- I look at
- Input data, timing and logs.
What I check at this point
Where does
the time go?
The application may be waiting for a query, a lock or another system. I check data access and its dependencies.
- The question
- Who is waiting for whom?
- I look at
- Queries, locks and paths to other systems.
What I check at this point
What actually
comes back?
Even a fast query is of little help if the response gets stuck afterward. I check processing through to the result the user sees.
- The question
- Does the complete result arrive?
- I look at
- Processing, transmission and error handling.
An example of troubleshooting.
03 / Personally
Since 2000.
Still curious.
I’m Herbert Röblreiter. Self-employed since 2000.
It started with web development and databases. Servers, networks and operations followed. This view beyond the individual parts helps me with new tasks.
You bring me in for a specific task. We agree directly on what I take on.
