Okay so a doctor from Germany contacted me (through a family member) about creating a presentation website for his private clinic but with a bit of a twist.

He did not want to use anything like wordpress or wix, but he DID want to be able to customize close to all the content of his website (not just text, even layout) and the content was also to be available in 3 languages EN | DE | RO.

I used the following technologies to implement all his requirements:
- SvelteKit
- MariaDB + Prisma ORM
- Json web tokens for admin dashboard authentication
- Tailwindcss for styling

Every single page of his website (he can even create more pages in the dashboard) contains sections that are fully editable in the /dashboard page of his app (he can change/write the whole HTML / CSS of each section individually, create other sections or delete them, preview them in the dashboard etc.) but it does not have a visual editor (that would be a bit too hard to implement).

Also as a bit of context the guy said he is comfortable enough writing HTML so he doesn't mind the fact that he has to edit it by hand instead of having a "visual" editor.

I asked 800€ for EVERYTHING which in my opinion was really little compared to the general market, but apparently he was VERY displeased with the offer thinking it was too much. Am I delusional or is he?

I see a lot of startups going into the hype cycle, which is understandable. But I also see so many webapps for resource planning, retrospectives etc. It’s either that, some AI thing, SaaS or something related to DevOps.

I see all this through ads or just looking at some local startups in my city.

Why does everyone want to make tools for making things instead of making a product in itself?

Seems everyone is selling shovels for other shovel selling businesses. Have we gone mad

Casual UK hates me, so I'm moving this here, as more people need to be aware of it.

I run a small old-school web forum, have done for about 16 years. While they're not as popular as they once were, there are plenty about - big ones like Mumsnet and Pistonheads, and little ones like beex.co.uk and many, many others.

Long story short, new OFCOM legislation is basically going to outlaw them in March (unless you have bags of cash to spend), and people are only just realising.

More info here: https://www.lfgss.com/conversations/401475/

This is the OFCOM page: https://www.ofcom.org.uk/online-safety/illegal-and-harmful-content/time-for-tech-firms-to-act-uk-online-safety-regulation-comes-into-force/

I've had an idea I wanted to bring to life since the beginning of covid. During lock down, I taught myself react and already knew some JavaScript so it was a fun journey. I created a static site, launched and didn't get much attention.

Fast forward to last year, I started working on my dream project, a full CRUD app. The motivation was tough to get while wireframing and creating one little feature at a time. A lot of back end work so the product isn't even visual most of the time. It was starting to weigh on me and with very little movement, I was questioning why I invested so much time and money into it (I'm paying for designers, awa, hosting, google workspaces, etc because I want to make this a viable business).

Well, now I get to actually build the visual elements and connect everything together. All the data movement, calculations/logic, and seeing the code running like an orchestra with me as the composer. It's a surreal feeling. After removing the placeholder images and text, plopping in the professionally designed assets, and playing around with the platform, I'm starting to see it come to fruition.

Last night, after developing for 8 hours, it was 1AM and I sat back to soak in all that I've done. I stared at my work, functioning, bug free and got a tear in my eye. Hours upon hours of debugging, refactoring, updating when I change the slightest thing, it was all there in front of me. I never thought I'd make it to this point. It's my passion project so there's much more satisfaction than coding for someone else.

This community has helped out and kept my passion for development alive as I read your stories and discussions. Some have even helped me on my quest. Thanks to all and happy holidays! Hope this will motivate you to continue working on your side projects.

Hello,

I've been told I would not come to work anymore as the company dismissed me from my front-end job. After 2 years of trying to become better It seems like I've failed to become someone you can trust. From what I've heard and understood, my biggest issue is my failure to perform in-depth testing - that did lead to too many hotfixes in production. It was also an issue in my previous jobs, so maybe I dont have what it takes to have a job like this? I feel a bit like im useless now, with no purpose.

Maybe I can work on this and try again in another company, but I dont know if its worth if I got to be fired once again.

Update: It looks like this post lack of context so let me add it for you below.

I did not have any authorization to push directly in production/staging. I only could self-approve my PR targetting dev. We did not have proper unit/E2E tests for FE. About existing process, it was:

1. dev testing his use cases
2. QA team testing again dev's use cases + some edge cases if they had in mind
3. PRs reviewed by another junior and then a senior dev before merging

I also would like to highlight that I've been put in a PIP, thus nuancing the company's responsibility. Accumulation of hotfixes/slowing down processes is was the root cause. Last month we did a 1-1 about the emergency to take action and fix those hotfixes behaviors. The day I knew I was dismissed was the day I was supposed to gather feedback from PO/design team before showing it to my manager during 1-1. Company just raised $30M in series B.

Do you actually enjoy coding?

Has somebody else felt like this? I’ve been programming since 2015, i’ve always been able to find solutions myself or just searching on the internet. Lately with copilot and some ai tool like gpt or claude i just feel like loosing my skills. Is the tradeoff worth it?

Have you felt like this?

This agency sucked. I left without a two weeks notice. They didn't pay the last week of my salary that I worked. Company is in Maryland. He ghosted me and didn't reply to requests for last paycheck. I'm filing with Maryland Department of Labor. He just sent this text:

"Merry Christmas to you and your family! Appreciate you leaving your review so that we can show - anyone who cares to ask about your words - the quality of your code and the work you provided for us. We had to double back over nearly all of your code and fix it. Cost us loads of time and money along with two very upset clients.

Could that be why you ghosted us? Were you taking us for a ride? If you recall, I supported you and made sure you were kept whole with care and reverence. Your ghosting us was quite unethical. You reap what you sow.

Happy to chat any time you’re ready but you asked for zero communication so we left you alone like you made very clear to us in writing.

We have no desire to throw you or your code under the buss publicly. So we will hold on a public reply and wait to see if you choose to communicate differently or maybe even remove your words. My phone is open and ready for your call any time.

Enjoy the holidays with your family and friends!

🎄🎅🏽🛷👼❤️"

Devs, don't let people bully you around.

Obviously you can work without a framework, but it might not be as optimal.

I miss when I was just starting out learning about HTM, CSS & JavaScript. It sucks that we don't do getElementById anymore. Things were alot more fun and simple.

I think is more easy to understand and more similar to HTML + CSS + JS courses that a component has a ts file, a css file and a html file than React JSX Soup. I don't say Angular is better only that I don't see the more hard learning curve.

A common convention I see everywhere is mapping /api/* paths to backend server via a reverse proxy.
For example, the frontend calls '$FRONTEND_URL/api/...', then a proxy server like nginx maps api/* routes to backend url.

What if the frontend directly calls the backend domain as in '$BACKEND_URL/api/...'?

Would this actually be a bad practice? Or is it simply not preferred because people end up having more complex scenarios to manage? I ask because this seems much simpler for my personal project setup where I don't have to deal with reroute or nginx rules, but I also want to make sure this is secure. Thanks in advance!

EDIT: Thanks for all of your answers! I reframed the question in body. I was wrongly using the terms absolute vs relative url. What I meant is directly calling the backend api domain from the frontend vs calling the same frontend domain and routing /api routes via proxy.

Title. Is adamant on having a pop up appear offering a discount for new clients. I told him it doesn't sound like a great idea because they're annoying. I said maybe a floating CTA button or just a prominent fixed CTA somewhere in the hero section as opposed to an actual pop up. Thoughts? Should I just do it for him?

I got this take-home after an interview with HR. It's for junior full stack dev position.

Task description:

Implement a messenger web application. The user should be able to log in/register and chat with other users one-on-one (no need to make group chats). The user should be able to attach multiple files to their message. be able to edit and delete their message. Authorization in the application is only by means of Express JS/Nest.JS.

Requirements:
Front-end: Angular/React + TypeScript
Back-end: Express JS, but NestJS is preferred
BD: Postgres/MySQL
Styles: Tailwind.
Deadline: 5 days + 2 days because of holidays.
The application should be dockerized.

There's also a technical interview after that.
Having browsed the subreddit, I came to a conclusion, that it's a rather big project for a take-home. But I'm curious if there're people here who completed similar take-homes and actually got hired? Were those jobs good and the take-home was the only hiccup or such take-homes are a guarantee that the company will exploit you 100% of the time?
I'm probably asking rhetorical questions, but there's a part of me that thinks "Suck it up and just do the job" if there's a chance that the company and the job might be decent.

I have been working on web/mobile development since ~2019 as a hobby. I took a course on HTML/CSS/JS and then moved into learning react and more recently react native. I’ve definitely improved over this time, and can make higher quality things faster. Recently I’ve been more serious about it and am trying to make stuff which could actually be used by other people. While I find the general process really fun and addictive, I notice that I also feel a lot of stress and burnout when I’m working on a project. But the thing is, I don’t feel that stress from the actual programming- dealing with errors and things not working the way I want etc. is stimulating if not fun, since I know that there is some error in my thinking that I need to resolve.

What frustrates me is constantly fixing a seemingly endless onslaught of environment/set-up related issues. For example, right now I’m trying to use the expo-linking module in my expo development build and am getting a “Cannot find native module ExpoLinking” error. “main” has not been registered. “A module has failed to load due to an error and ‘AppRegistry.registerComponent’ wasn’t called.”

Lately it feels like my time spent programming has been 20% actually writing code and 80% jumping between stackoverflow questions trying to resolve issues like this, fiddling with package.json when I don’t really understand what I’m doing. What is the name for this sort of problem?

Is this simply what web development is like? Does it get easier? I am passionate about what I create so I usually just grind through these issues and slowly move forwards. I think I’m better at resolving these issues than when I started 5 years ago, or at the very least am suffering because I’m taking on more and more sophisticated projects.

But to some extent I worry that I have a fundamental lack of knowledge which severely slows me down. I’ve only ever done this as a hobby which has mostly meant ‘learning by doing’ rather than ever actually sitting down and properly studying any of it. Is that what I need to do? What are the best resources for doing this? I study computer science at university but they don’t touch any of this sort of stuff.

I am currently working on a cooking website, which is an online recipe book which hosts a variety of recipes, each with a video tutorial on how to make it. There will be around 300 recipes. The webdev is thinking of using Supabase for the backend, nextjs for the front end and an external video host like Vimeo for the videos. It also needs to handle accounts and payments (stripe) as it is a membership service. He has all the UX UI wireframes already. What will be a reasonable price to ask for this to be developed? But more importantly how long would this be expected to take?

Edit - I’m Leaning away from Wordpress since I see this as more of a SaaS web app compared to a static blog that hosts recipes. It’s more of an educational site where users learn specific skills in cooking through recipes which range through easy to hard. It won’t be completely static in the sense that it will be interactive through giving the user the ability to filter recipe difficulty, type, cuisine etc. So like a hybrid cooking course style site but much less structured. I want the webdev to code a dynamic system where adding recipes is easy (apparently this is called a CMS?) so that they do not have to be entered manually each time after new content is added.

Hey guys, I have been going through a situation for the past 5 months or so.

So, I am a webdev for about 3 years now, started at a small startup using pure js and php, like the good old days and then switched to my current company using Java and JSP, working on a big fintech company here where I live.

The thing is, I entered the programming world while young, at my 16 years I discovered that I could make games by my own if I sat down and learned programming, and that's what I did, started with a local game development course that was shutdown due to the lack of interest from local teens. Switched my course to some more generic but still related to IT.

As I said, nowadays, I work as a full-time java developer, but my dream always has been of developing games, idc if it's a small studio, big studio or just going indie with a few friends, and I feel that I'm stuck with java for fintech stuff and this thought has made me get stuck, I'm close to being not productive at work, before I start a task I get myself just studying c++ or something else, I really want to change, but idk what to change.

Should I change myself and try to at least enjoy what I do or try to get out of this situation?

I am newbie dev and I do not understand the need of paying for npm so far. I think my use case is different from people who pay for it so i wanna understand their use case better.

After 4 months of running a technical content agency and working with various dev tool companies, I've noticed a massive disconnect between what companies think developers want and what they actually need. Here's what we've learned:

What companies think developers want:

• Comprehensive API references
• Basic "Hello World" examples
• Feature listings
• Marketing fluff about being "developer-first"

What developers actually want:

• Real-world implementation examples
• Migration guides from competing tools
• Performance implications and trade-offs
• Known limitations and workarounds
• Integration patterns with popular tools
• Clear troubleshooting flows

The biggest revelation came when we started doing user interviews. Almost every developer said something along the lines of: "I don't read documentation to learn your tool. I read it to solve a specific problem."

This completely changed how we approach documentation:

1. Every major feature now has:
   • Common use cases
   • Integration examples
   • Troubleshooting guide
   • Performance considerations
   • Migration examples
2. We organize docs by user intent rather than features:
   • "I want to migrate from X"
   • "I need to integrate with Y"
   • "I'm trying to solve Z problem"
3. We maintain a living "gotchas" section based on:
   • GitHub issues
   • Discord/Slack questions
   • Stack Overflow posts
   • Support tickets

The results have been significant. One client saw their documentation-related support tickets drop by 60% after implementing these changes.

Would love to hear your thoughts.

What makes documentation actually useful for you? What makes you trust a tool enough to use it in production?