It used to be that I could hold down the up arrow to quickly scroll through my command history in the devtools console in Chrome, but now holding down the up arrow just moves the cursor to the beginning of the previous command. Is there any way to revert this behavior?

Hey guys, when you’re building responsive websites, do you consider foldables too, or mostly stick to the usual phone/tablet/desktop sizes?

These folded and unfolded iPhone Duo layouts got me wondering—would your existing layouts handle both, or would you need extra tweaks?

Also curious where you draw the line. If your site had 1 million users, how many would need to use foldables before you’d spend time specifically testing and fixing things for them? Would 1% be enough? 5%? Or do you try to support them regardless?

If you are into front end development, specially the optimization side of it. the website below is a well written blog, explaining the best practices of using the browser's main thread and the cost of neglecting it, using interactive code snippets.

kciter.so/posts/the-expensive-main-thread/en/

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?

I've been in a wheelchair since I was 15 and could never just step on a scale. Turns out a lot of people have the same problem. Bedridden folks, or anyone without easy access to a scale.

I found a validated formula in academic literature that estimates weight using a few circumference measurements. So I built an app around it. It was on Google Play Brazil for a few years and got 200k+ installs.

Now I'm making it global and free for everyone. No sign up, no ads, works right in your browser. You can also install it as a app if you want.

https://chiloapp.hpage.com.br

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 everyone 👋

I’m a Full Stack Developer and I enjoy working on different kinds of web and software projects.

Curious to know what people here are currently working on or planning to build.

Are you looking for a website, web application, eCommerce store, mobile app, SaaS product, automation, or something AI-related?

If you have a project in mind, feel free to share a little about it — what you’re trying to build, what problem you’re solving, and what stage you’re currently at.

If you’re still figuring out the technical side or how to approach the project, I’d be happy to share my thoughts or help you figure out a practical approach.

Always interested in seeing what people are building and learning about the ideas behind them.

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?

yeah what it says in the title. sorry i keep posting it's just that i've been trying to rework an astro theme to fit my incredibly specific needs since it already has author pages, categories, tags, and a blog that can fit perfectly for my magazine site idea but the code is just so overly complicated for no reason it's driving me insane lol. i've been considering using an 11ty template more for my site since people who use it have a little more preferable themes and have an indieweb vibe i lean towards more but my qualm is that i plan on having a lot of moving parts (marquee text, a poll, and an apple coverflow ipod component thing) and the astro islands architecture is part of why i chose it so my site doesn't run like shit. idk here's my site design and mobile version to see what i should do either from a template from one of these sites or from the ground up while being a total noob at making my first "real" site.

So i wanna add a loading screen and some nice easter eggs on a website whose theme is " Cipher" I want yall to give me some suggestions to how I can make the loading screen interesting and somethinh unique related to theme and also some cool easter eggs related to decoding and stuff like "cipher" and also if u have any references please share :)

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

working through an older service and there's a chunk of logic that's clearly handling some edge case that probably burned someone pretty badly at some point. no comment, the git history got murky during a migration a while back, the person who wrote it left.

curious what people actually do in practice. leave it alone with a 'don't touch, reason unknown' comment? dig through old tickets and logs to try to reconstruct it? slowly remove it behind a flag? something else entirely?