Serkan Özcan

Latest posts

#Apple · #MacBook Pro · #Steve Jobs · #touchscreen · #OLED · #Technology

Jobs said "It doesn't work": now Apple is selling a touchscreen MacBook Pro

October 20, 2010. At Apple's "Back to the Mac" event, the company is explaining which ideas Mac is borrowing from iOS. The question is already hanging in the air: if the iPhone and iPad are used with a finger, why can't…

Read
#PHP · #Cybersecurity · #Open Source · #Artificial Intelligence · #System Administration

What the PHP crisis taught me: Security is a shared responsibility

The recent PHP vulnerabilities should make everyone who develops software or runs servers reconsider their responsibilities. When we put a working application online, we also take responsibility for maintaining it and…

Read
#PHP · #Cybersecurity · #PHP2Shell · #Security updates

PHP2Shell: Disclosure is not when the risk begins

PHP2Shell refers to CVE-2026-109618 and CVE-2026-109619, two critical vulnerabilities that can allow unauthenticated remote code execution in affected PHP installations. Security updates were released on October 21,…

Read
#Cybersecurity · #PHP · #Security advisory · #System administration

Türkiye’s official PHP warning: A practical response for organizations

The Turkish Cybersecurity Presidency’s PHP security bulletin TR-26-1372, dated 21 October 2026, calls on organizations to review their PHP systems. My previous post covered the technical vulnerabilities; here I want to…

Read
#PHP · #Cybersecurity · #Security Updates · #Technical Analysis

PHP’s critical security alarm: Two flaws and the reality of patching

The PHP security alarm in the October 22, 2026 news cycle concerns the language runtime beneath websites, rather than a defect limited to one application or extension. CVE-2026-109618 and CVE-2026-109619 can allow…

Read
#Artificial intelligence · #Muse Spark Open · #Local AI

Muse Spark Open: open weights, local inference, and real costs

Downloading a model and running it in your own environment creates another area of control in AI products. It can give you more direct influence over data flows, runtime behavior, and integrations. Accessible weights,…

Read
#Artificial intelligence · #Anthropic · #Independent evaluation

Internal access for AI oversight: Anthropic's next step

Testing an AI system through external questions alone may not reveal all the risks visible inside its developer. How the model was developed, how safeguards operate, and how previous incidents were handled can all affect…

Read
#Artificial intelligence · #Materials science · #Science

When AI reads crystals: a three-dimensional view of materials discovery

Knowing a material's chemical name is different from understanding how its atoms are arranged. The same components can behave differently in different structures. Materials research therefore contains an important layer…

Read
#Artificial intelligence · #Anthropic · #Technology economics

Anthropic's public benefit fund: sharing the gains from growth

As AI companies grow, who receives the economic value they create becomes a more concrete question. I find the public benefit fund announced by Anthropic on October 18, 2026 interesting because it aims to link its…

Read
#Artificial intelligence · #Child safety · #Digital privacy

Child safety in AI apps: an age label is not enough

An app being available in a store or carrying an age-appropriate rating does not establish that all its features are safe for children. AI image editors make that gap more visible: a seemingly ordinary editing interface…

Read

Something to discover

3 articles
Automation · 8 Oct 2026 · 2 min read

Small automations, more room to breathe

Automation may bring complex systems to mind. Yet the starting point is much more ordinary: a small task we repeat throughout the day.

Observe for a week first

Before automating a process, we need to see how it really works. Two tasks that look the same may have different exceptions. Even simply recording repetitions for a week can reveal where to focus.

  • Which step happens frequently?
  • Where are mistakes more likely?
  • How do we notice when the process fails?

The smallest useful workflow

The first automation only needs to do one thing well. That might mean organizing a file, reporting a change in status, or reducing manual data transfer between two systems.

A reliable workflow should have a clear failure path as well as a success path. It should be obvious when it runs, what it does, and how to stop it when something goes wrong.

Good automation reduces repetitive work while keeping us in control.

Leave a way back

For tasks that affect real devices or important data, it helps to start with a narrow trial. Recording changes, using a dry run where possible, and keeping a way to do the task manually make things easier.

The goal is not to build a workflow for everything. It is to make a little more room for the work we really want to give our attention to.

Loading…