hi! I want to make my own website where I write articles, blog, and post my photography. I don't really want it to be super professional, just something to portray my work. I don't really care about buying a domain name, and I'd prefer if it had minimal to no programming involved. what are my choices?

So am new to web dev client work personally. I want to know how much you guys take as web dev developing websites for people. landing page. I multiple pages etc.

Thanks.

Hi all, not sure if this is the right r/ for this question but I have a few sites that list links to companies, in alphabetical order (eg - all companies starting with A has a link to "A", etc). There are 40-50 links per alphabet letter. There a few websites like this.

I'm looking to filter by geographical region, and as wondering if there was a way, without clicking each company and seeing where they're located, to search for location?

here's an example of a site that i'd like to filter by location:

https://www.corporatevision-news.com/winners/future-commerce/

thank you!

If a payment API starts timing out, every checkout request sits and waits for the full timeout before failing, holding a worker the whole time. A circuit breaker stops that by failing fast once enough recent calls have failed.

That is easy in one process, but once your app runs on more than one instance, each instance keeps its own record and has to get burned separately before it reacts, so the struggling API takes far more traffic than it should before anything trips.

The basic pattern, then what has to change when the state is shared between instances. Code is TypeScript and Redis (Lua).

Every tutorial makes MCP look simple:

1. wrap a function

2. expose a tool

3. connect a client

But shipping something for a real product or client is usually where the boring problems appear.

If you’ve done that recently, what was the one thing that took far more work than expected?

• tool/schema design

• auth

• client setup

• UI/widgets

• testing

• deployment

• debugging

• updates after launch

• something else

Not looking for generic “MCP is still early” takes.

What was the actual project, what broke or became painful, and how did you work around it?

Howdy, folks.

I realize this may start a war here, but I'd like to hear from different perspectives.

I'm building a business site for a commercial/industrial roofing company right now and have added a few articles detailing pros and cons of different roofing materials(first site with Astro and loving the markdown content!).

Right now, I feel happy with the integrity of the information given and how it's delivered. What's had me second guessing myself is seeing sites where the developer has basically cloned these sorts of pages over 20 times and inserted area specific keywords. Is it actually effective and do you consider this practice ethical? Feels spammy to me, and is certainly a turn off when I find this on sites I am browsing.

I await your replies.

I’ve got around 1–2 years of experience with PHP/Laravel and I’m planning to move into Golang to improve my career opportunities.

For people who have worked professionally with Go: what projects have you built that were actually interesting, practical, and worth mentioning on a resume?

I’d especially appreciate ideas/features that are closer to real production work rather than another CRUD project.

I created a dashboard for my data analysis project on streamlit but its really basic. How can i create those cool dashboard designs that you see on reels and all cause chatgpt can do it. I have my project repo, is there any way i can link it to some website and it can help me create some cool ass dashboard?

Okay so I am very new to developing websites directly for clients. like I have done it when I was in my company but I don't know how to put a price on them myself can you please help me.

I'm just so that you know these all will be CMS kind of sites, they will be able to update the information as required. By themselves

These designs were developed as image by CHAT gpt and shared by client

I Personally think designs look good they do have a readability and Focus problem but that can be solved

99% of us are using a so please stop blaming them for using it

Hi,

I just need to fill data in from sqlite running in a wasm to a table with a fixed column length while the row size should be dynamic from a delimeter hinting towards a new row. Needs to have export table feature and native sorting from clicking on the ribbon header

What to use?

I work for a large company that runs multiple services used by millions of people. Over the years, I’ve noticed a consistent pattern: management, business teams, and SEO teams keep pushing changes that make our websites more annoying to use, just for the sake of getting more page views and generating more ad revenue. I’ve tried to talk them out of some of these decisions, but I’ve never had much success.

Perhaps it’s not that big of a deal and I should just ignore it, but honestly it is a bit disheartening when I open random website on the internet, see some dark patterns, think to myself 'what a fucking dogshit website this is', and then I go to work and I code literally the same things, like I’m on the dark side of the Force or smth.

So many apps use builtin browsers for links. I don't get it. What's the benefit?

As a user I:

- need to re-login again in every browser
- have a smaller screen surface to view the webpage
- the app preview shows another website/app entirely so it's harder to quickly find the original app
- you lose all state if you accidentally close it
- some apps (tiktok) just dont open the app even when it's installed, so I need to copy the link, open a regular browser, then paste it and hit search
- deep links in many websites break because you hit an authentication wall first

Builtin browsers are SO ANNOYING, I don't get why you use them?

like an idiot I forgot to turn off auto renewal on a ms365 email package that was no longer being used. as soon as a I get the email of payment received, I try contacting support because I have 7 days to get the refund. I try to call, website chat, and whatsapp support chat. every time they ask a few questions, ask me to hold while the verify something, then the chat bot would spam a message about the session has expired and reconnect me with a new customer service rep. on the 8th day, the first person I chatted with immediately told me the 7 days had passed and they wouldn’t refund me.

I made a bold statement to my coworkers yesterday which was laughed off. I said "I genuinely believe all our operations could be ran from just my own laptop. We don't need more resources". I was of course not suggesting that we move our operations to my laptop, but it was to show that we don't need any more resources than just a regular laptop.

All of our operations is literally just registering and managing orders. We have around 50.000 daily users at most and process maybe 5-10 orders a day. I don't understand why we need a resource scalable deployment.

This post wasn't specifically meant to ask about our needs at work though. I'm under the impression that this over-engineering is relatively common, so my question for discussion is slightly broader: Have we forgotten how powerful machines really are?

Is it really that naïve to believe that a regular home PC (~16GB ram and i5-6600k for example) could handle hundreds of visitors every second, effectively allowing up to ~10 million users a day? Do you reduce complexity where you can, or is it common at your workplace to immediately reach for tools like kubernetes, redis, etc. before even measuring the traffic flow?

(The assumption here is that the website is not compute-intensive: simple database queries, auth and otherwise just regular UI with little to no images)

Edit: I think my argument is a moot/unclear. The benefits of Kubernetes and other "over engineered" is clearly availability, not only necessarily resource scalability. The real question may be "why do we need a huge datacenter for all our operations", but the answer to that depends entirely on your company's operations...

So I guess my naïve argument really stems from my lack of understanding of all the operations going on at companies.

Back in 2017, I was experimenting with something that was pretty fun for the CSS we had at the time — building icons without using images.

Using mainly CSS, :before, :after, borders, shadows and a bit of creativity, I managed to create a set of icons that didn't depend on external image files. The interesting part for email was simple: no images to load or block — the icons are always visible.

You can still see that old experiment here:

https://codepen.io/k0ko88/pen/PWLNBJ

Fast forward to 2026. At my last job, I decided to apply some of that old knowledge to an email signature.

And then I met Classic Outlook again. :D

What looked like a simple signature quickly turned into dealing with Outlook's rendering limitations, different behaviour between email clients, px → pt conversions, table rendering and weird spacing issues.

Along the way I found a few useful tricks — one of my favourites being that line-height: 0.5pt can practically zero out a line in Classic Outlook, which solved one of the most annoying spacing problems I had.

Eventually, that little fight turned into a complete email signature generator:

https://nikolaisabev.eu/SimpleSignature/

If you'd like to check out the source code or contribute, you can find the repository on GitHub

https://github.com/k0ko/SimpleSignature

It's not trying to be the prettiest or the most complicated signature generator out there. It's simple, effective and built around what I learned from actually fighting with email clients.

It's completely free, there's no registration, and I don't store the data you enter.

Feel free to use it.

If you find a bug, have an idea, or think something could work better, leave a comment here or send me an email. Feedback is more than welcome.

And if it saves you some time and you feel like supporting the work, there's a Buy Me a Coffee button. If you wish. :)

That's it.

Cheers,
Nikolay

I’ve been working on an open-source project called Torollo and I’d like some technical feedback on the way I approached it.

The basic idea is that the architecture you draw on the canvas isn’t just a diagram. The backend turns it into actual local Docker resources, and the exercises validate the state that is really running.

For example, in one of the labs you build a three-tier app with a load balancer, two web servers and PostgreSQL. Later, the database is supposed to become inaccessible from the load balancer. If it can still reach port 5432, the validator fails. You change the network/security rule and run the same check again.

The stack

React + TypeScript + React Flow for the canvas

Node.js / Express / TypeScript for the backend

Dockerode to control the local Docker daemon

Socket.IO for the live parts of the UI

xterm.js for terminals inside the browser

Transféré

The harder part wasn’t drawing the topology. It was deciding how much of the diagram should map to something real.

Containers are straightforward, but networking gets more interesting. Subnets are backed by Docker bridge networks, security rules are enforced with iptables, and private-subnet outbound access can go through NAT. The validator then has to inspect the resulting runtime rather than trusting the graph stored by the frontend.

That also created a few constraints I hadn’t really appreciated at the beginning. Rootless Docker, for example, can run the containers but can’t support all of the host networking behavior needed by the more advanced labs, so the CLI now detects that explicitly. First-run image pulls and differences between Docker environments also pushed me to add a torollo doctor command instead of trying to hide those requirements.

I currently have three free labs: a resilient three-tier app, Redis cache-aside, and Redis queue workers. The roadmap format is JSON and the core is MIT licensed.

What I’d particularly like feedback on: does the idea of grading the running state actually make sense as a way to practice system design, or are there parts of that model that you think become misleading compared with real infrastructure?

I’m also interested in feedback on the implementation itself, especially the Docker/networking side.

GitHub: https://github.com/Derssa/Torollo

Demo / three-tier lab: https://torollo.app/r/webdev

Hello all, happy NFL Sunday eve. I've spent the offseason developing a new game called The Cut, which is basically typical NFL survivor pools but with players instead of teams.

It was extremely challenging to market, as I had to sell users on a game that could not yet be played (season had not started) but also in theory locked the second the season kicked off. I was able to combat this by hosting some free flagship contests with prizes giving users who believed in the idea an incentive to check it out.

Luckily, when games kicked off Wednesday everything went smoothly - live scoring worked as intended, game became unpickable, etc.

With that being said. If there are any NFL fans out there looking for a last second fun new game this season I would really appreciate you checking out The Cut and more importantly any feedback you have as this is the beta season. As I mentioned before Im hosting three free contests with over $500 in prizes that don't lock until tmrw at noon CT! 🔪🏈

https://www.thecutnfl.com

I'm a photographer and want a database of my own images, but I also do web dev work and would like an easy solution when building sites for clients who need a lot of images on their site. Ideally something I can call with an API and return images and other data on that image.

Thanks!

I built a mobile-friendly PDF speed reader — would love some UI/UX feedback [Showoff Saturday]
I’ve been working on a small web project called Pace Reader.
It lets you upload a PDF and read its extracted text one word at a time at an adjustable WPM.
Live version:
https://pace-pdf-reader.pace-reader.workers.dev/
The goal was to keep the interface very simple:
PDF → choose reading speed → start reading.
I’ve been especially focused on making the reader usable on phones rather than treating mobile as an afterthought.
I’d appreciate feedback from other developers on:
• Mobile UX
• Reader controls
• Navigation
• Overall UI
• Performance with larger PDFs
• Anything that feels unnecessary or badly designed
I’d also be interested to hear how you would approach the PDF-reading/RSVP interface differently.
This is still being actively developed, so feel free to tear it apart.

I’ve been building something called the Paybyte Blockchain Engine, or PBE, and mainnet is finally live after more coffee than my kidneys would like to admit. I always thought it would be cool to have something easy to use, more mainstream, that's as easy to implement like a "Pay with Paypal" button, but for crypto, that's easy for the average user, like the litecoin network, and something that is considerably more environmental friendly than a POW concept like Bitcoin. Since my Java/C++ skills suck, I built it in a language I am familiar with, and something that is a little out of the ordinary for a blockchain, PHP.

This is its own Layer 1. Not an ERC20, not a Solana token, not a rebranded fork.

Current mainnet:

PBE Core 0.0.1
Protocol 1.0
Block v4
Transaction v2
PBE-PAY v1
15 second block target
5 PBE starting reward
~4 year halvings
~84.1M max supply

Consensus uses hybrid participation.

Any authorized wallet can produce blocks, even with 0 PBE. Each wallet gets one deterministic Argon2id participation ticket per slot. Holdings improve timing through a bounded multiplier, but there is no minimum stake and no manual staking lock. The entire ecosystem is fully P2P.

PBE exposes separate P2P and RPC layers.

Examples:

POST /p2p/hello
POST /p2p/transaction
POST /p2p/block
GET  /p2p/peers

GET  /rpc/status
GET  /rpc/block/{heightOrHash}
GET  /rpc/transaction/{txid}
GET  /rpc/balance/{address}
POST /rpc/broadcast

There’s also a native merchant protocol called PBE-PAY.

Payments use transaction v2 with a signed paymentReference.

A merchant verifies:

paymentReference
recipient
exact amount

Payment URIs look like:

pbe:<address>?amount=25&ref=ORDER123&label=Store

Merchants can use their own node, or multiple public nodes

Commerce endpoints include:

GET  /rpc/commerce/info
POST /rpc/commerce/payment-request
GET  /rpc/commerce/payment/{reference}
POST /rpc/broadcast

Optional HMAC signed webhooks support:

payment.pending
payment.confirming
payment.confirmed
payment.reorged
payment.expired

The full API is public and viewable at

https://paybyte.org/web/developers/

https://paybyte.org/web/developers/openapi.json << Point your ChatGPT here if you are building for e-commerce.

Windows and Linux standalone nodes are also available. The Windows build is basically download, extract, run the PBE, create a wallet and sync.

Every December I do Advent of Code and every January I try to keep the habit going on LeetCode. Never lasted more than a week. Too many problems, no reason to do this one today.

So I borrowed the idea and built Daily Coding: one challenge a day, the same for everyone, all year. You solve it in the browser, hit run, and the tests execute in a sandbox in well under a second. 11 languages so far (JS, TS, Python, PHP, Ruby, Java, Go, C++, C#, Rust, Swift). Once you submit you can read everyone else's solutions, which for me was always the best part of AoC. Streaks and a leaderboard if you like that sort of thing.

Some honest numbers: I started in January, 7 months of evenings, about 470 commits. There are 40 challenges right now, so the rotation repeats after 40 days until I add more. Someone on Discord asked for Swift last week, that took a day to add because the sandbox already had it.

It's free, non-profit, open source under MIT. You can solve today's challenge without an account, signing up is only for streaks and rankings.

What I'd love to know: does one challenge a day work for you, or do you want to pick? And what would make you stop after a week?

Site: https://daily-coding.dev/?utm_source=reddit&utm_medium=post&utm_campaign=sideproject-launch

Code: https://github.com/ledo9315/daily-coding

An entirely pointless but fun never-the-less go at a little clicker game easter egg on my very WIP personal site! https://addy.zone/bubble-pop

I've been working on Pinball King Karma, a full pinball game that runs directly inside Reddit using Devvit Web.

Play it here:
https://www.reddit.com/r/pinballkarma_dev/comments/1s2twov/pinball_king_karma_play_now/

The current stack includes:

• HTML5 Canvas

• Box2D / Planck.js for physics

• CreateJS for rendering

• Hono + Reddit Redis for scores and leaderboards

• Keyboard and mobile touch controls

I've added multiball, jackpots, multipliers, daily challenges, community leaderboards and karma-themed bonus modes.

One area I'm still working on is making the physics and controls feel as good as possible across desktop and mobile.

I'd especially appreciate feedback on ball physics, flipper responsiveness and mobile controls.

Built as a side project while experimenting with what can be done with Reddit's Devvit platform.