chrishannah.me

The web (World Wide Web) is a system of interlinked documents and resources, accessed over the internet using browsers and identified by URLs. It is one service that runs on top of the internet, not the internet itself. This explanation covers the core building blocks, what happens when a page loads, and how to tell "web" apart from "internet," "browser," and "search engine."

Web vs. internet vs. browser vs. search engine

These terms get used interchangeably, but they describe different things:

A useful analogy: the internet is the road system, the web is one type of traffic that travels on it, the browser is your car, and a search engine is a directory that tells you which roads lead where.

Email, video calls, and many mobile apps also use the internet but are not the web. Email, for instance, relies on its own protocols (like SMTP) rather than web pages.

The core building blocks of the web

URLs

A URL (Uniform Resource Locator) is the address of a resource on the web. A typical URL has parts that each do a job:

https://www.example.com/products/item?id=42

• https — the protocol (how to communicate)
• www.example.com — the domain (which server to contact)
• /products/item — the path (which resource on that server)
• ?id=42 — a query string (extra parameters)

HTTP and HTTPS

HTTP (Hypertext Transfer Protocol) is the set of rules browsers and servers use to exchange requests and responses. HTTPS is the same protocol wrapped in encryption (TLS), so the data can't be read or altered in transit. Most sites today use HTTPS, and browsers flag plain HTTP as "not secure."

Browsers

A browser turns code into the pages you see. It sends requests, receives files (HTML, CSS, JavaScript, images), and renders them into a visual layout. It also manages cookies, caching, and security warnings.

Web servers

A web server is a computer (and the software on it) that stores web content and responds to requests. When you visit a page, your browser asks a server for files, and the server sends them back.

What happens when you load a page

1. You enter a URL or click a link. The browser reads the address.
2. DNS lookup. The domain name (like example.com) is translated into an IP address so the browser knows which server to contact.
3. Connection. The browser opens a connection to that server, using HTTPS if available.
4. Request. The browser sends an HTTP request for the specific resource.
5. Response. The server returns the requested files and a status code (for example, 200 for success, 404 for not found).
6. Rendering. The browser parses HTML, applies CSS for styling, runs JavaScript for interactivity, and draws the page.
7. Follow-up requests. The page may request additional resources — images, fonts, scripts — before it's fully loaded.

If any step fails, you see an error: a DNS failure means the domain couldn't be resolved; a timeout means the server didn't respond; a 404 means the server responded but the resource wasn't there.

Where the web fits in everyday use

The web is what you're using when you:

• Open a site in a browser to read, shop, or log in
• Follow a link from an email or message
• Use a web app (a service that runs in the browser rather than as an installed program)
• Watch a video embedded on a page

It is not what you're using when you:

• Send or receive email through a mail client
• Make a phone or video call over the internet
• Use an installed mobile app that talks to its own servers

Those still depend on the internet, but they don't require a browser or web pages.

Common confusions, cleared up

• "The web is down." Usually a specific site or your connection is down, not the entire web.
• "I found it on the internet." If you found it through a browser and a URL, you found it on the web.
• "My browser is the internet." The browser is a tool for accessing the web; the internet is the underlying network.
• "A search engine is the web." A search engine is one website among many that helps you navigate the web.

Quick reference

• Web = linked documents and resources accessed via browsers over the internet.
• Internet = the global network that carries many services, including the web.
• Browser = software that requests and displays web content.
• URL = the address of a web resource.
• HTTP/HTTPS = the rules for exchanging web requests and responses; HTTPS adds encryption.
• Web server = the machine that stores and serves web content.

Understanding these distinctions makes it easier to describe problems accurately, choose the right tools, and follow technical instructions without mixing up the layers.

Developer marketing is the practice of reaching software developers where they already learn and make tooling decisions—technical content, creator channels, open source, and community—and turning that attention into product signups. It differs from traditional marketing because the audience evaluates tools on technical merit, tries before trusting, and ignores polished ad copy. It's the right approach when your product is an AI or DevTools offering and your bottleneck is distribution rather than product quality.

Why distribution, not product, is usually the bottleneck

Most AI and DevTools teams are founded by people who can build. The failure mode described by DevTools Academy is "Great Product, Broken Distribution"—the tool works, but the people who would use it never hear about it in a context they trust.

Developers don't convert on impressions. They convert after seeing a credible peer use the tool, reading a technical walkthrough, or watching someone solve a real problem with it. That means the marketing job is not persuasion—it's placement in front of the right technical audience with proof attached.

How developer marketing differs from traditional marketing

The practical consequence: budget spent on speculative reach tends to underperform compared to a systematic creator partnership framework, which is the shift DevTools Academy describes making for Orchids.

The creator-led distribution model

Creator-led developer marketing means partnering with technical creators who already have the audience you want, rather than buying reach through ads. DevTools Academy runs this across YouTube, X, LinkedIn, Instagram, TikTok, Reddit, UGC, and technical newsletters.

The mechanics that make it work:

• Credibility transfer. A creator who understands the tooling explains it in their own voice, so the recommendation carries weight an ad cannot.
• Depth over volume. The goal is "developers, not just impressions"—a smaller, engaged technical audience beats a large passive one.
• Repeatability. A creator program built once can produce consistent output quarter after quarter instead of one-off spikes.

For Stream, this approach was credited with 6,600+ sign-ups across every quarter of FY-2025, with a program built from the ground up spanning 60+ creators across YouTube, X, LinkedIn, open source, and newsletters.

What execution looks like end to end

DevTools Academy frames its work as "end-to-end developer GTM execution" and "numbers, not narratives." A workable sequence for a team running this themselves:

1. Identify where your developers already are. Pick the two or three channels where your target users actually spend time—not all of them at once.
2. Recruit creators with technical credibility. Prioritize people who can use the product and explain it, over reach alone.
3. Give them something real to show. A working integration, a benchmark, or a solved problem produces better content than a feature list.
4. Let the content run in the creator's format. Tutorials and demos outperform scripted promotion on technical channels.
5. Measure signups and engagement, not just reach. Track comments, reposts, and sign-ups per channel so you can reallocate.

How to measure whether it's working

The evidence from DevTools Academy's case studies points to a measurement set that goes beyond impressions:

• Signups — the primary outcome. Stream: 6,600+ sign-ups across FY-2025 quarters.
• Engagement depth — comments and reposts as a signal of real technical interest. Oumi's LinkedIn launch produced 631+ comments and 269+ reposts on day one.
• Impressions and engagements at scale — Orchids reached 1.1M impressions and 10,000+ engagements in a single quarter.
• Consistency over time — growth that repeats every quarter, not a single viral moment.

Oumi's founder described the value as watching "the comment section turn into a deep-dive discussion on day one"—that discussion is the social proof that drives the next wave of signups.

When this approach fits

Creator-led developer marketing is a strong fit when:

• Your product is an AI or DevTools offering aimed at working developers.
• The product is good but under-distributed.
• You can support a program over multiple quarters rather than a single campaign.
• You're willing to trade speculative spend for a structured creator framework.

It's a weaker fit if your buyers are non-technical, if you have no working product to demonstrate, or if you need results within days rather than a quarter.

Where to start

If you want to assess your current position before committing, DevTools Academy offers a "See how your current GTM stacks up" entry point alongside strategy calls and published case studies. The useful first step for most teams is auditing which channels already produce signups, then concentrating creator partnerships there instead of spreading across every platform at once.

A programmer is someone who writes, tests, and maintains the code that makes software run. The title covers a wide range of work — from building a website feature to fixing a bug in a mobile app — and it overlaps heavily with "developer," "engineer," and "coder." If you're trying to understand the role before hiring, learning, or applying for a job, the practical answer is this: a programmer turns a described problem into instructions a computer can execute, then keeps those instructions working as requirements change. The rest of this article breaks down what that involves, using a working developer's public writing as a concrete example.

Programmer vs. developer vs. engineer vs. coder

These terms are used loosely and often interchangeably, but the differences are worth knowing when you read a job listing.

In practice, a "programmer" at a small company may do everything a "developer" does, while at a large company the title may signal a narrower focus on implementation. Treat the label as a rough signal, not a strict boundary — the responsibilities in the job description matter more than the word in the title.

Core skills and tools programmers actually use

The specific stack varies by employer, but the categories are stable.

Languages. Most programmers know one or two languages well and can read several others. Common starting points are Python, JavaScript, Java, C#, Go, and Swift. The language matters less than the ability to learn a new one when a project requires it.

Editors and IDEs. An editor is where you type code; an integrated development environment (IDE) bundles an editor with debugging, build tools, and project management. Which one you use is largely preference and team convention.

That choice is not fixed. Chris Hannah, a developer who writes at chrishannah.me, published a post titled "Do I Need an IDE Anymore?" — a question that reflects how capable lightweight editors and command-line tooling have become. The takeaway for a newcomer: learn the fundamentals of editing, running, and debugging code, and treat any specific IDE as a tool you can swap out.

Version control. Git is the near-universal standard. You'll use it to track changes, branch work, and collaborate.

Debugging and testing. Reading error messages, reproducing bugs, and writing tests are day-to-day skills, not side tasks.

What the day-to-day work looks like

A typical day mixes several activities rather than long uninterrupted coding sessions:

• Writing code against a ticket, spec, or bug report
• Debugging — reproducing an issue, isolating the cause, and fixing it
• Reviewing other people's code and responding to review comments on your own
• Reading existing code, documentation, and error logs to understand a system
• Shipping — merging, deploying, and confirming the change works in production
• Communicating — clarifying requirements, estimating effort, flagging blockers

The balance shifts with seniority. Junior programmers spend more time writing and debugging; senior ones spend more time on design, review, and coordination.

Career paths and specializations

Programmers tend to specialize over time. Common directions include:

• Web — frontend (what users see), backend (servers and data), or full-stack
• Mobile — iOS, Android, or cross-platform
• Backend and infrastructure — APIs, databases, deployment, reliability
• Data and tooling — pipelines, internal tools, developer experience
• Specialized domains — embedded systems, games, security, machine learning

Some programmers move into adjacent roles: engineering management, product, developer relations, or independent building. Hannah's blog is an example of the last path — alongside writing about code and culture, he documents building and maintaining his own product, a blogroll platform called Miniroll, covering features like embeddable blogrolls, aggregated RSS feeds, and a JSON API. That kind of side project is a common way programmers broaden their skills beyond a single employer's stack.

How to start learning and build a portfolio

1. Pick one language and finish something small. A working command-line tool or a single web page teaches more than three unfinished tutorials.
2. Learn Git early. Put every project in a repository from day one.
3. Build in public where you can. A blog, a README, or a changelog shows how you think, not just what you shipped.
4. Read other programmers' writing. Developer blogs are a low-cost way to see how real projects evolve — including the parts that go wrong. Hannah's posts, for instance, describe a UI revamp driven by specific complaints (blocky layouts, overused monospace fonts) and the fixes applied (rounded borders, higher-contrast accent colours). That is the kind of concrete iteration a portfolio project should show.
5. Contribute to something you use. Fixing a bug in an open-source project you rely on is a credible first collaboration.

Common misconceptions

• "You need a computer science degree." Many working programmers are self-taught or came through bootcamps. A degree helps with some employers and some specializations, but it is not a universal requirement.
• "Programming is mostly typing." Most of the work is reading, understanding, and deciding. Typing is the smallest part.
• "You learn a language once." Languages, frameworks, and tools change. The durable skill is learning new ones quickly.
• "It's solitary." Most professional programming is collaborative — reviews, standups, and shared codebases.

If you want a single sentence to hold onto: a programmer is someone who solves problems by writing code, and stays valuable by being able to read, debug, and adapt code they didn't write.

ray.so turns a code snippet into a styled image you can export and share. Paste your code into the editor, pick a theme and window style, adjust the layout, then export the rendered result as an image. This works best for short snippets you want to post on social media, in docs, or in chat — not for long files, since the image grows with the code.

Before you start

• Have the code snippet ready to paste, and know which language it's in so the highlighting matches.
• Decide where the image will live (a post, a slide, a README). That tells you whether you want a background, a light or dark window, and how much padding.
• Keep the snippet short. A few dozen lines read well as an image; hundreds do not.

Step-by-step

1. Paste or type your code

Put the snippet into the editor. Check that the syntax highlighting matches your language — keywords, strings, and comments should be colored, not flat text. If the colors look wrong, the language isn't being detected correctly; adjust it before you style anything else, since the theme you pick later depends on it.

2. Choose a color theme

Pick from the available syntax color themes. This controls how the code itself is colored. Choose one with enough contrast that the code stays readable when the image is scaled down in a feed or a slide.

3. Toggle the window and background

• Dark or light window — switches the frame around your code between a dark and light appearance.
• Background — show or hide the colored background behind the window.

If you're posting on a light page, a light window with no background blends in; a dark window with a background stands out. Match this to where the image will appear.

4. Adjust padding, line numbers, and window controls

• Padding — the space around the code inside the frame. More padding gives a calmer, more presentable image; less padding fits more code.
• Line numbers — turn them on if you or your readers need to reference specific lines; turn them off for a cleaner look.
• Window controls — the traffic-light buttons on the frame. Keep them for a familiar editor look, or hide them for a more neutral image.

5. Export the image

Export the rendered snippet as an image and let the file download. Before you post it, open the downloaded file and check:

• The code isn't clipped at the edges.
• Highlighting is present and correct.
• The background is the one you intended (not blank or missing).
• Text is still legible at the size it will be displayed.

Common export problems and fixes

When this is the right tool

Use ray.so when you want a single, self-contained image of a short snippet that looks polished without design work. Skip it when the code is long, when readers need to copy and run it (share a gist or repo instead), or when you need the code to stay searchable and accessible as text.

Forbes treats technology as a business beat, not a product-review desk. Its tech coverage focuses on how technology companies make money, raise capital, compete, and change industries — with AI, enterprise software, startups, venture funding, semiconductors, cybersecurity, and consumer platforms as recurring subjects. It is most useful when you want the strategic or financial angle on a tech story; it is less useful when you need benchmarked device testing, hands-on reviews, or deep technical specifications.

The Main Tech Subtopics Forbes Covers

Forbes' own description places technology alongside business, investing, entrepreneurship, and leadership, which explains why its tech stories rarely stand alone. Common subject areas include:

• AI and enterprise software — corporate adoption, vendor competition, and how AI tools affect business operations.
• Startups and venture capital — funding rounds, founder profiles, valuations, and exits.
• Big Tech companies — strategy shifts, earnings-driven narratives, executive moves, and regulatory pressure.
• Cybersecurity — breaches, security spending, and the business of protecting data.
• Semiconductors and hardware — supply chains, chipmakers, and infrastructure.
• Consumer platforms and devices — usually framed around market position, company strategy, or user behavior rather than specs.

What Forbes Tech Coverage Is Not

Forbes is a business media company, not a lab. That distinction matters when you decide where to spend your reading time.

If your question is "should I buy this device?" or "how does this protocol work?", Forbes is usually the wrong first stop. If your question is "why is this company making this move, and who profits?", it is often the right one.

How the Business and Investing Angle Shapes the Reporting

The same technology can appear in a Forbes tech story and a Forbes investing story with different framing. A chip announcement might be covered as a competitive move against rivals, a signal about capital expenditure cycles, or a factor in earnings expectations. This means:

• Company moves are read as strategic bets, not just product news.
• Funding and valuation numbers carry weight, because the audience includes investors and entrepreneurs.
• Leadership decisions matter, since Forbes also covers leadership and entrepreneurship.
• Trend pieces tend to connect technology to revenue, cost, or market share.

For a reader, this is an advantage if you are tracking an industry or a company's direction. It is a limitation if you want neutral technical evaluation.

Using Forbes Tech Coverage to Track Trends and Company Moves

A practical way to get value from this coverage:

1. Pick a company or sector you follow — for example, enterprise AI vendors or chipmakers.
2. Read the tech story for the strategic claim — what the company is betting on and why.
3. Cross-check the financial framing — does the article tie the move to revenue, funding, or competition?
4. Note what is missing — product performance, independent testing, or technical depth.
5. Fill the gap with a specialized outlet if you need hands-on or technical verification.

The expected result is a clearer picture of why a technology matters commercially, with an explicit note of where the evidence stops.

When Forbes Tech Articles Are Useful — and When to Go Elsewhere

Use Forbes tech coverage when:

• You are following a company's strategy, funding, or competitive position.
• You want technology framed through business, investing, or leadership.
• You need trend context rather than product detail.

Go to specialized tech outlets when:

• You need reviews, benchmarks, or hands-on testing.
• You want deep technical explanations or specifications.
• You are comparing products on performance rather than market position.

The practical rule: Forbes answers "what does this mean for the business and the market?" Specialized outlets answer "how well does this actually work?" Knowing which question you have tells you where to read first.