do u think microshoft will one day shut down github for public and bring us subscription services?

as if there are not enough out there.

i just got a gut feeling last night, loging into github and cruising the night...how i imagine a window pops up and tells me yo, you forgot to pay your sub this month. go get the money or we have to delete your whole history on git.

i had the same feeling decades ago with adobe software and see what happend.

why else would ms even have an interest in a website like github at all.

our entire discipline - whether you use Scrum, Kanban, or whatever flavor of Agile - relies on predictable states. We write requirements, we define boundaries, and we build tests to ensure those boundaries hold.

But right now, management wants "AI" embedded in core workflows. Not just for chatbots, but for routing, data validation, and state transitions.

you cannot write a reliable Definition of Done for a probability matrix. If a stakeholder says "the system must enforce these three compliance rules" you can't guarantee that with an LLM. You either end up writing a massive, brittle wrapper around the model, or you just accept that your CI/CD pipeline is now a slot machine

It feels like a massive step backward for software methodology. We spent decades building robust testing frameworks just to throw them out because the generative output looks confident

If we are going to use AI in core business logic, the underlying architecture has to respect constraint satisfaction. the shift toward Logical Intelligence frameworks seems like the only sane path forward - treating business rules as hard mathematical boundaries the system literally cannot violate, rather than just hoping a prompt holds up in production

do you just pad your estimates to account for prompt-engineering hell, or are you actively pushing back against product owners who want generative AI running deterministic tasks?

I did a gcp course 18 months ago and I have totally forgotten it. Anyone like me ?

I've been a solo dev running a platform with 15K users for 2+ years. Early on, I tried to follow every "best practice" I read about. It nearly killed my productivity. Here's what I stopped doing and why:

1. I don't write unit tests for everything Controversial, I know. But as a solo dev, I write integration tests for critical paths (auth, payments, data mutations) and skip unit tests for simple CRUD. My integration test suite catches 95% of bugs in 1/5 the time. Time is my scarcest resource.

2. I don't use microservices A monolith on a single EC2 instance handles 15K users just fine. The operational overhead of microservices (service discovery, distributed tracing, network failures, deployment coordination) would triple my workload for zero user benefit.

3. I don't do code reviews There's no one to review my code. Instead, I write a PR description explaining why I made each decision, wait 24 hours, then review it myself with fresh eyes. I catch most issues this way. The 24-hour rule is the key.

4. I don't use Kubernetes Docker Compose on a single server. That's it. K8s is incredible for teams managing dozens of services at scale. For a solo dev with one app, it's like buying a semi truck to deliver groceries.

5. I don't separate staging and production databases I use a single MongoDB Atlas cluster with separate databases (prod and staging) in the same project. This saves ~$60/month and the data isolation is sufficient for my needs. The risk is manageable for a solo operation.

The principle behind all of this: Every "best practice" has an implicit context — usually a team of 5+ engineers working on a system with millions of users. As a solo dev, my constraints are completely different. I optimize for shipping speed and operational simplicity.

The best architecture is the one that lets you ship and iterate fastest given YOUR constraints.

What "best practices" do you deliberately skip? Or am I playing with fire here?

https://static.klipy.com/ii/8ce8357c78ea940b9c2015daf05ce1a5/01/2d/n0oyg3fz.gif

The horror of this realization, being mostly pro-AI in moderation (and acutely aware of how some countries monitor ppl on camera already), is certainly a dark side of AI. Never thinking for yourself, always having to make decisions from the list of options given, building things exactly a specific l, pre-programmed way leads to lack of ingenuity and stagnation. That's borderline oppression, but it's so, SO MUCH worse because it's invisible to us. We don't feel like it's a violation, yet. It's just slipping into our daily culture like it's normal. THAT part is the scary bit.

So last night while i was using the live server it randomly crashed on Chrome saying Aw Snap! something went wrong error code: Out Of Memory

So far I’ve practically spent all day clearing space and unnecessary memory. With chrome and VS code open task manager says my memory is at 54%.

I’ve restarted my computer multiple times and I’ve even changed the paging file size in advanced performance option to 12,000 - 15,000.

I’m kind of at my wits end here. I’m not even sure if this is a memory issue because my laptop does everything else at regular run times except open a html file in a web browser. It doesn’t work on edge or Firefox either.

My computer has 8gb of ram installed and there’s still an additional 3.5gb of ram available right now.

Are there any resources out there for me to speak on the phone with someone that could walk me through how to fix this?

At this point I’m thinking I might have to save all my files somewhere and do a hard reset.

Oh- I even tried to use Repl.it for the time being and the live server on there crashed too.

Edit: my bad I was unknowingly running an infinite loop in my code

Been developing on Mac for a long time. I have to say I'm getting more impressed with Windows than Mac. WSL has come a long way from its original inception and Mac's Unix system is still very weak. Mac was really good 3-4 years ago.

WSL lets me build out many virtualized Linux systems within itself and it behaves much like my Unix input on a mac but on Windows. I have visual studio code executing from within Windows into the WSL environment. I can also back up and restore this WSL environment if I bork it bad.

If I was writing something graphical I can still see Mac having that ground, but I feel development has become more and more agnostic. The quality in Mac has dropped significantly when it used to be the office king. It didn't really drop, the standards and expectations only became greater.

What is everyone's 2022 take on Mac vs Windows, not considering Linux because of too many flavors?

Ever feel like the true Agile is just a never-ending game of "who’s got the best buzzwords"? Waterfall’s still around, making developers drown one step at a time. And don’t get me started on Scrum - where you’re lucky if the only sprint is the one to the coffee machine. Let’s be real: can we just code already?

Hey everyone, I just wrote up a tutorial on building ChatGPT from scratch. I know this has been done before. My unique spin on it focuses on best practices. Building ChatGPT the right way.
Things the tutorial covers:

• How ChatGPT actually works under the hood

• Setting up a dev environment to iterate on prompts and get feedback as fast as possible

• Building a simple System prompt and chat interface to interact with our ChatGPT

• Adding logging and versioning to make debugging and iterating easier

• Providing the assistant with contextual information about the user

• Augmenting the AI with tools like a calculator for things LLMs struggle with

Hope this tutorial is understandable to both beginners and prompt engineer aficionados 🫡

The tutorial uses the PromptLayer platform to manage prompts, but can be adapted to other tools as well. By the end, you'll have a fully functioning chat assistant that knows information about you and your environment.

Let me know if you have any questions!
I'm happy to elaborate on any part of the process. You can read the full tutorial here: https://blog.promptlayer.com/building-chatgpt-from-scratch-the-right-way-ef82e771886e

See what happened to Python.

Lately in our teams, I’m hearing some confident takes from business analysts and product owners that AI tools will mostly impact developers and testers… because apparently business folks will soon be able to build, test, and ship features themselves using AI.

But honestly, if business folks are eventually designing, building, and validating solutions end-to-end using AI… then what exactly happens to the need for Business Analysts and Product Owners? 😀

Is anyone else hearing similar assumptions in their teams? How realistic do you think this is?

I've seen developers spend months preparing to launch.

One more feature.
One more redesign.
One more rewrite.

Then another month disappears. I understand it.

We want the thing we build to be good. But I've learned that perfection can become another form of procrastination.

Real users will teach you things your codebase never will. Build it well. But put it in people's hands.

been working with businesses on software problems for over a decade. The ERP and CRM disconnect is one of the most expensive invisible problems I keep seeing and almost nobody has calculated what it is actually costing them.

Sales closes a deal. The CRM says won. Someone then manually copies the order details into the ERP. A field gets entered wrong. Or it gets entered a day late. Finance is working from numbers that do not match what sales sees. The operations team is fulfilling based on information that is already slightly out of date. Customer support is looking at a different screen than the person who actually spoke to the client.

Nobody's system is wrong exactly. They are just not talking to each other. And the person in the middle doing the copy paste is not adding value. They are just being a human API.

the businesses I have seen fix this always say the same thing afterwards. They wish they had done it two years earlier. Not because the integration was complicated but because they had no idea how many small decisions were being made on bad data every single day.!

What is the version of this that lives in your business right now???

What’s the go-to “vibe-coded slop” app in your industry?

The obvious ones for me are notebook/notetaker apps and so-called intelligent dashboards.

What other examples have you seen?

Saw this post https://www.reddit.com/r/devops/comments/1d9pwgw/do_your_developers_develop_on_production/ in the devops subreddit and I was wondering if the non-devops-oriented developers (like myself) have different thoughts

I prefer pushing things right to my prod servers to see they work. sometimes making a snapshot of the database to test things out, sometimes just pushing it there for a little bit and rolling it back if it breaks things.

if you tend to go straight to prod like I do, what does your setup look like? have you ever been able to do it at a large company with other engineers as well or just for personal projects?

If I have to be forced to rummage tons of code in search of "bad" terms like master/slave or blacklist, at least I'd like to know if the proposals to change that jargon come from a bunch of, let's put it this way, opinionated activists, or there is at least a significant minority that agrees with it. So, are there opinion polls on the issue, having some kind of statistical reliability?

I live in Ukraine although I am American, I want to start a software development business I am not a programmer myself but I meet many talented programmers who have relatively low salaries. I thought about starting a outsourcing business but after several attempts find it relatively hard to find clients, although I still find the idea appealing. I have access to cheap and a good labor force and several thousand dollars to invest in is outsourcing a good avenue, or starting a CRM, building apps, SAAS a better business idea and if outsourcing is good should I niche down like do some specific niche like QA, web dev, dev ops etc?

There is a lot of people saying web agencies are saturated and the business is dying. I been running my web agency for 4 years and not gonna lie I was thinking the same for 3 of those years. A lot of failures, no consistent clients, no predictable income and honestly I thought maybe this business model just doesn't work anymore.

But there are a few things I changed that helped me scale past 20k a month.

The first thing was switching from targeting businesses with no websites to businesses that already had one. The reason this worked way better for me is because there are sooo many businesses with outdated websites that clearly need updating. And the second reason is they already understand the value of having a website because they already went through the process of paying for one before, so its way easier convincing them to get a better version instead of convincing someone from zero.

The second thing I started doing was offering a free draft redesigned version of their current website. I mean realistically who says no to free. I build them quickly using AI and most of the time they already look way more modern and better than the ones they currently have. Once they see a better version of their own business in front of them, making them pay becomes the easy part.

Another thing that changed everything was how I presented the websites. I used to just send preview links through email and that was honestly the biggest mistake. They check it later when they are busy, there is nobody there to explain things properly or push them toward buying so eventually the lead just goes cold.

Now I always present the websites live on google meet and close them on the spot. That alone made a massive difference.

Also always charge upfront for building the website but don't ignore monthly recurring revenue. Hosting, changes, maintenance etc. That's important if you actually want stable income every month instead of constantly chasing new clients.

For the people interested in the tools I use, it's pretty simple honestly.

Apollo for finding leads because you genuinely never run out of businesses to contact.

Swokei for outreach. I upload the lead list there and it analyzes each business website, scores it and turns flaws in design, seo, speed and mobile optimization into personalized ready to send emails automatically. I run all my outreach campaigns there.

Ai for building websites. And honestly the people saying Ai websites dont perform well are mistaken. You can pretty much build anything now if you know what youre doing.

Cloudflare for hosting client websites.

Thats honestly it.

If anyone wants to know more about how I do everything feel free to reach out :)

Hey folks,

I'm diving into the world of internal technical documentation and want to hear your war stories! We've all been there - staring at a screen full of jargon, outdated info, or steps that make about as much sense as a broken compass.

What are the BIGGEST problems you face with technical documentation? Is it the organization? The writing style? Maybe it's the sheer lack of documentation altogether?

I'm looking for your real-life experiences to understand the pain points. The more details, the better!

So, what are your tech doc horror stories? To be transparent, I hope to collect the major pain points when it comes to technical documentation in yet another effort to solve it for us fellow developers. Tired of **Yet Another Linear Looking Confluence lookalikes**.

P.S. Feel free to share any good documentation experiences you've had too! Those are gold nuggets as well.

For some people we can just tell will be 10x engineers. They have a super-solid foundations, a great intuition and an uplifting spirit about problems. For some people, it's harder to make such predictions. Over time, a few will surprise us and become one of the greats.

I would like to know – as mentors, how should we approach this? What are some pitfalls, what are key best practices? Do you have some great stories?

E.g. is hyping up someone that they can be 10x really helpful if they actually can't be 10x?

Note: when referring to 10x engineers, I'm not necessarily saying their output is 10x. Is more a synonym for engineers that are the top 1%

Does anyone else have an issue with the Senior Engineers? I came in with a mindset to learn from those with greater experience, and time spent on the systems we develop. I feel that the tech I grew up with is the standard, and maybe some older engineers never had the time / energy to keep themselves up to date. Today my proposal for a CI / CD pipeline was shut down by the Head of Back-End development as the pipeline he never finished over three years ago (two server changes required (test & live) - £5k - £10k+ hence the delays likely), is supposedly going to work one day. He convinced my Head of Department (also head of service (she doesn't code so there we go)) to close both my tickets. The younger engineers seem to get it a little more. I feel the system my team has had for longer than I've been there will be taken off us since the client is becoming our biggest client thanks to my team's work (not mine personally - they fixed the dogs**t this person and his team left in there for us from 2017). FYI my pipeline was built and tested in three days - it wasn't even complex! Oh, and there is also a remote access backdoor in the digital signage products we ship which removed my name from the waiting list for the VPN (smoke mirrors) which should be the only way to access. I fixed a drive-thru at midnight with this backdoor.

https://medium.com/@needablackcoffee/my-top-10-development-tools-e191b8efabe9

Code Vaulter, Code Vault inclusee, etc.?

i tend to get into disagreements easily whenever the topic is "clean code". we're supposed to write it, but there's no objective way to measure it. my anti-favorite is "SOLID"

half of that isn't even defined. what is a responsibility, for example? doesn't SRP taken literally mean i can never do business logic AND log things in the same class?

i read somewhere "don't introduce classes when you don't have to."

but i never have to. i can use hashmaps for everything. or just stringly type everything.

i like to "just solve the actual problem and write self explanatory code", totally disregarding explicit clean code principles. who is with me?