masswerk.at

Consulting is an advisory service in which an outside professional diagnoses a problem, recommends a course of action, and often helps implement it — rather than simply executing a task you hand over. You should consider hiring a consultant when you face a specific problem you can't solve internally, a deadline that exceeds your team's capacity, a skills gap, or a decision that benefits from an outside perspective. The sections below explain how consulting differs from related services, the situations that justify it, how engagements are typically structured, and how to choose and manage a consultant well.

What consulting actually is

A consultant's core product is judgment applied to your situation. The work usually follows a recognizable arc:

1. Diagnose — understand the current state, constraints, and root cause of the problem.
2. Recommend — propose options with trade-offs, not just a single answer.
3. Implement (often) — work alongside your team to put the recommendation into practice.
4. Transfer knowledge — leave your team able to sustain the result.

The emphasis on diagnosis and recommendation is what separates consulting from pure execution. If you only need someone to perform a defined task, you may want a freelancer or an outsourced provider instead.

Consulting vs. related services

These categories overlap in practice, but the primary deliverable differs:

A single provider can wear more than one hat. The useful question is what you're actually buying: advice and problem-solving, skill development, task completion, or ongoing operations.

When hiring a consultant makes sense

Common triggers include:

• A specific problem — costs are rising, a process keeps breaking, or a system isn't delivering what it should.
• A project deadline — you have the knowledge internally but not the bandwidth.
• A skills gap — the expertise you need is specialized or temporary, so hiring full-time doesn't make sense.
• An outside perspective — internal politics or familiarity make it hard to see the problem clearly.
• A high-stakes decision — a second, experienced opinion reduces the cost of getting it wrong.

If none of these apply — the work is routine, well understood, and you have the capacity — a consultant is likely unnecessary overhead.

Typical engagement models

• Hourly — best for short, unpredictable questions or a small diagnostic. You pay for time, so scope discipline matters.
• Project-based (fixed fee) — best when the deliverable is well defined. You get cost certainty; the consultant carries scope risk.
• Retainer — best for ongoing advisory needs or continuous access to expertise. You pay for availability, not a specific output.

Match the model to how well you can define the work. The fuzzier the problem, the more a diagnostic phase (often hourly or a small fixed fee) helps before committing to a larger engagement.

How to choose a consultant

Check these before signing:

• Relevant credentials and certifications — confirm they exist and are current for the field in question.
• Industry or domain experience — ask for examples of similar problems solved.
• References — speak to past clients about results and working style, not just satisfaction.
• Scope of work — get deliverables, timeline, assumptions, and what's not included in writing.
• Communication cadence — agree on check-ins, reporting, and who your point of contact is.

Common failure points and how to avoid them

• Unclear scope — define deliverables and boundaries in writing before work starts.
• Missing deliverables — tie payments to milestones or outputs where possible.
• Poor communication — set a regular cadence and a single point of contact on both sides.
• No knowledge transfer — require documentation or training so the result outlasts the engagement.
• Unclear success criteria — agree upfront on what "done" and "successful" look like.

Quick decision guide

Hire a consultant if you can answer yes to at least one of these: you have a problem you can't solve internally, a deadline you can't meet, a skills gap that's temporary, or a decision that warrants outside expertise. Skip it if the work is routine, well understood, and within your team's capacity — in that case, a freelancer or an outsourced provider is usually the better fit.

Norbert Landsteiner is the founder of mass:werk, and masswerk.at is the corporate home page of that practice, covering design, web development, and consulting. It is a personal and company site rather than the official site of a single product, so the fastest way to use it is to treat it as a portfolio and demo hub: read About for background, browse Products & Demos for the work, and use Contact if you want to get in touch.

Who Norbert Landsteiner is

The site identifies mass:werk as the corporate home page of Norbert Landsteiner, with the listed activities of design, web development, and consulting. The site's own keywords also name N. Landsteiner as an alternate form of the name, alongside retro computing and computer history. That combination is the useful summary: a designer and developer who also builds and writes about historical computing.

If you arrived looking for a company with a large team or a product brand, adjust expectations. This is the working home of one practitioner, and the site is organized around his projects and experiments.

What the site is for

masswerk.at works as a navigation hub. The menu gives you the main areas:

The home page excerpt also surfaces a set of named demos and tools: Play Spacewar!, ELIZA, Talking PET 2001 Emulation, Virtual 6502, JS/UIX, Google BBS Terminal, and Google 60. These are the concrete things you can open and try, not just descriptions.

What you can actually do there

The demos fall into a few recognizable groups, which helps you decide what to open first.

Games and playable classics

Spacewar! is listed as something you can play directly. If your interest is early computer games, this is the most direct entry point on the site.

Emulations and conversational programs

ELIZA, the early conversational program, and a Talking PET 2001 emulation are both listed. These are reconstructions or emulations of historical computing experiences rather than modern applications, so expect period-appropriate behavior and interfaces.

Tools and technical experiments

Virtual 6502 and JS/UIX are listed among the tools. Virtual 6502 relates to the 6502 processor family, a chip central to home computers of the late 1970s and 1980s. JS/UIX is a JavaScript-based Unix-like environment. Both are the kind of thing you open in a browser to explore, not install.

Novelty and web-history pieces

Google BBS Terminal and Google 60 present Google-style interfaces in retro forms. They are best understood as design and web-history experiments.

How to use the site efficiently

1. Start at the Home page and read the menu, since the site is organized by section rather than by product.
2. Open About if you need to know who is behind the work before evaluating it.
3. Go to Products & Demos to see the full set rather than only the items highlighted on the home page.
4. Pick a demo by interest: games for play, ELIZA and PET 2001 for historical computing, Virtual 6502 and JS/UIX for technical exploration.
5. Use Contact only after you have a specific reason to reach out, such as a design, development, or consulting inquiry.

A practical check: if a demo does not load or behave as expected, confirm you are on the current page for that demo from Products & Demos rather than an old bookmark. The site lists these as demos and tools, so they are meant to run in the browser.

When this site is the right stop

masswerk.at is worth visiting if you want to see the work of Norbert Landsteiner, try browser-based retro computing demos, or evaluate whether to contact him about design, web development, or consulting. It is not the place to look for product documentation, pricing, or a support desk; the site presents the practice and its experiments, and the Contact entry is the route for anything beyond that.

mass:werk (masswerk.at) is the corporate home page of Norbert Landsteiner, described on the site as covering design, web development, and consulting. It is also a personal hub for browser-based retro computing and game experiments. Use this page to confirm the site's identity and to locate its main sections and interactive demos; it is not a product storefront or a service-purchase page.

Who runs the site

The site identifies itself as the corporate home page of Norbert Landsteiner, with design, web development, and consulting as its stated areas. The site's own keywords also list "retro computing" and "computer history," which matches the interactive content described below.

Main navigation sections

The home page menu lists these sections:

If you are looking for a specific demo, start with Products & Demos; the menu alone does not list every item.

Interactive demos and tools on the home page

The home page surfaces direct links to several browser-based experiences:

• Spacewar! — a playable version of the early computer game.
• ELIZA — the classic conversational program.
• Talking PET 2001 Emulation — an emulation of the Commodore PET 2001.
• Virtual 6502 — a 6502-related tool.
• JS/UIX — a JavaScript-based Unix-like environment.
• Google BBS Terminal and Google 60 — terminal-style and period-style experiments.

These are demonstrations and experiments, not commercial offerings. A page titled like a product demo does not mean the site sells that product or service.

Consulting vs. demos: how to tell them apart

The consulting side of mass:werk is described at the site level (design, web development, consulting) and is reached through About and Contact. The demos, games, and emulators are separate entertainment and exploration content. If your goal is to inquire about work, use Contact; if your goal is to try something in the browser, use the demo links or Products & Demos.

Practical notes

• All listed entries are reachable from the home page menu or its link list; no login is mentioned on the page.
• The site is in English.
• The page provides no pricing information, so do not assume any service or demo is free or paid based on the home page alone.

Web design is the practice of planning how a website looks, reads, and behaves for the people who use it — covering layout, visual style, typography, color, navigation, and the overall user experience. It is distinct from web development, which builds the working site in code, though the two roles overlap heavily in practice. This explainer is for anyone trying to understand the discipline, evaluate a designer, or decide whether to hire one.

What web design actually covers

A web designer's work is not just "making it pretty." It typically includes:

• Information architecture — deciding what pages exist and how content is grouped.
• Layout and grid — where elements sit on the page and how they align across screen sizes.
• Visual style — typography, color palette, imagery, spacing, and brand consistency.
• Navigation and interaction — menus, links, buttons, and the flow between pages.
• Responsive behavior — how the design adapts from desktop to tablet to phone.
• Accessibility — contrast, readable text sizes, keyboard navigation, and semantic structure.
• User experience (UX) principles — reducing friction, making actions obvious, and matching user expectations.

Web design vs. web development

The two are often confused, and the boundary is blurry. A useful distinction:

Many practitioners, especially on small projects, do both. A designer who can write CSS can hand off work that is far easier to build.

Core skills to look for

• Typography and color — readable type scales and palettes that meet contrast standards.
• Grid and layout systems — consistent alignment rather than ad-hoc placement.
• Responsive design — designing for multiple viewport widths, not just one.
• Accessibility awareness — WCAG basics such as contrast ratios and focus states.
• UX thinking — understanding the user's task before choosing a visual style.

A typical workflow

1. Requirements and goals — what the site must achieve and for whom.
2. Content and structure — sitemap, page inventory, and priority content.
3. Wireframes — low-fidelity layout sketches to agree on structure before styling.
4. Visual mockups — high-fidelity designs applying type, color, and imagery.
5. Prototype and review — clickable flows to test navigation and key interactions.
6. Handoff — specs, assets, and style guidance for the developer.

The expected result at each stage is a decision the next stage depends on: structure before style, style before build.

How to evaluate a design

• Usability — can a first-time visitor find the main action without instructions?
• Consistency — do repeated elements (buttons, headings, spacing) behave the same way?
• Performance awareness — are images and fonts chosen with load time in mind?
• Accessibility — is text readable, contrast sufficient, and navigation keyboard-friendly?
• Responsiveness — does it hold up at narrow widths, not just on a large monitor?

When to hire a designer

Hire a web designer when the site's structure and presentation are the bottleneck — a new brand, a confusing navigation, or a site that looks dated or fails on mobile. If you already have a clear design and only need it built, you may need a developer instead. For a broader look at when outside expertise is worth it, see the related question on consulting.

Where mass:werk fits

mass:werk (masswerk.at) is the home page of Norbert Landsteiner, described as covering design, web development, and consulting, alongside retro computing and computer history projects. It is a useful example of a practitioner whose work spans both design and development — and whose site also hosts interactive demos and historical emulations. If you are researching individual designers or small studios, that kind of combined profile is common.

N. Landsteiner is Norbert Landsteiner, and masswerk.at is the home page of his practice, mass:werk, which the site describes as covering design, web development, and consulting. If you are trying to put a name to the site, confirm that you have the right person, or find a particular demo or tool, the home page is the place to start: it is a portfolio and project hub rather than an encyclopedia entry about him.

Who Norbert Landsteiner is

The site presents mass:werk as Landsteiner's corporate home page and lists design, web development, and consulting as its areas of work. The site's own keywords also connect the name to retro computing and computer history, which matches the kind of browser-based projects hosted there.

That combination is the useful takeaway: he is a designer and web developer who also builds and writes about historical computing. The site does not publish a biography, a client list, or rates on the home page, so treat it as the entry point to his work rather than a full profile.

What you can find on masswerk.at

The home page is organized as a menu of sections, each leading to a different kind of content:

Two clusters stand out if you arrived through the retro-computing keywords:

• Playable classics and emulations. The menu names Spacewar!, ELIZA, and a Talking PET 2001 emulation, all running in the browser.
• Tools and experiments. Virtual 6502, JS/UIX, Google BBS Terminal, and Google 60 appear alongside the games.

The excerpt also repeats "Google BBS Terminal," so expect some overlap or duplication in the menu rather than a strictly one-entry-per-item list.

How to use the site depending on what you need

• Checking who someone is. Open About first; it is the section intended to explain mass:werk. Use Contact if you need to reach Landsteiner directly.
• Looking for a specific demo or tool. Go to Products & Demos for the project list, or Games if you want something playable. Names like Virtual 6502 and JS/UIX are the quickest way to confirm you have found the right item.
• Following his writing. The Blog is the section for longer-form posts and updates.
• Just exploring. The Lounge and the games are the low-commitment way in; the emulations and terminal experiments are the most distinctive part of the site.

What the site is not

masswerk.at is not a general reference page about Norbert Landsteiner. It does not present itself as an encyclopedia entry, and the home page gives no pricing, service packages, or booking details. If you need commercial terms or availability for consulting or development work, the site points you to Contact rather than publishing them, so any arrangement has to be discussed directly.