THE neurofunken BLOG

Think openly.
Share what we learn.

Perspectives on software, Linux, SI, and the digital work ahead — with a clear position, traceable sources, and ideas grounded in daily work.

Follow articles via RSS

Explore articles

33 articles

An access card and laptop are handed over while setting up a workplace.neurofunken / ideas

SSO is not offboarding: why SCIM has a separate job.

Connect your application to a customer's identity provider. Test sign-in, roles and the account lifecycle separately.

Read more
Application versions A and B share a database across three transition phases.neurofunken / ideas

A software update needs a transition phase.

New application, existing database: how you plan changes in stages, account for old versions, and recognise the limits of a rollback.

Read more
A website turning into a workflow of steps someone completes at a laptop.neurofunken / ideas

Your company website can take work off your hands — if it gets a job.

A customer portal pays off when people can complete the same process there reliably. How you find the entry point and clarify rights, interaction, and operations before you build.

Read more
Server room with an open exit door, backup boxes, and a completed restore checklist.neurofunken / ideas

Open source without a tested exit is only a good feeling.

Licence freedom alone does not make you independent. Only exports, complete backups, and a dry run with clear acceptance criteria make an operator change plannable.

Read more
Filing cabinet and server with revisions, sync in between, and an error ticket for human review.neurofunken / ideas

Changing a field is easy. Keeping the context is the work.

Website, editorial, and line-of-business systems share data — but not the same ownership. How you plan leading systems, revisions, and error paths so integrations stay dependable.

Read more
Open Linux workplace with browser and terminal on the monitor — chosen deliberately, not by default.neurofunken / ideas

Windows by default? Omarchy asks a better question.

The default workstation deserves a reason. Omarchy shows what an open Linux desktop can look like, and how to assess whether a migration makes sense.

Read more
Desk with a named task on a sticky note, measuring tape, and checklist — SI needs a clear job first.neurofunken / ideas

SI helps when the task has a name.

A useful first application starts with an everyday task you can assess. Choose the model afterwards. Optimism needs a way to measure progress.

Read more
Laptop with a questionable code suggestion beside printed code a hand is reviewing and correcting.neurofunken / ideas

SI writes code. You keep responsibility.

Generated code often looks finished. Quality depends on understandable changes, independent criteria for checking them and someone who can explain the decision to adopt them.

Read more
Three doorways: handing over papers, handing over a key, then meeting at a desk — transitions in people work.neurofunken / workshop

palmscout: work begins before the contract is signed.

A workshop note on the product vision. palmscout connects recruiting, HR and staffing, with decisions tested against practical handovers between people rather than feature lists.

Read more

A good place to start.

neurofunken knowledge assistant

Hello! What would you like to improve? I can explain our services and help you find a useful next step.

Replies from our editorial knowledge base.

Please do not enter confidential information. Privacy

Blog · Open source, software & digital work · Page 3 · neurofunken