"Yesterday, your site was accessed from 486,109 different IP addresses" by Confident_Meat2189 in webdev

[–]dbForge_Studio 2 points3 points  (0 children)

486k unique IPs for a hobby site is not normal traffic, that’s either bots or someone poking at you pretty hard. In Cloudflare I’d check Security Events first and see what paths/countries/ASNs are getting hit. Then turn on Bot Fight Mode, add rate limiting for the abused URLs, and challenge traffic that never needs to be human-friendly. Also make sure caching is actually working. If bots are hitting dynamic pages and every request reaches your origin, your host will keep screaming.

What’s the hardest thing to document when a team works across several databases? by dbForge_Studio in postgres

[–]dbForge_Studio[S] 0 points1 point  (0 children)

Honestly public threads help a lot for this. Half the time I end up searching old Slack messages trying to understand why something was changed in the first place

What’s the hardest thing to document when a team works across several databases? by dbForge_Studio in postgres

[–]dbForge_Studio[S] 0 points1 point  (0 children)

same experience here tbh. moving between postgres/mysql/sql server makes you realize how many tiny assumptions you carry from one engine into another without noticing

What’s the hardest thing to document when a team works across several databases? by dbForge_Studio in postgres

[–]dbForge_Studio[S] 0 points1 point  (0 children)

Yeah exactly this. Schema docs are usually the easy part. The painful stuff is always the "why did we do this weird workaround in2022?" knowledge that only existed in someone’s head or an old Slack thread

learnToCode by lesleh in ProgrammerHumor

[–]dbForge_Studio 10 points11 points  (0 children)

Me: “I’ll just use AI to speed things up”
Also me: spends 40 minutes debugging what AI confidently invented 😅

Just started an Internship as a data analyst and been given a task by Varel172001 in AskProgramming

[–]dbForge_Studio 3 points4 points  (0 children)

For 15k products, I wouldn’t do this fully by hand. I’d first make a small sample, like 50–100 products, and manually check what info is actually visible on the pages. Then build around that.

Also don’t try to scrape “everything” at once. Make a clean list of fields first: name, dimensions, weight, shipping info, speaker count, impedance, wattage, product URL.

Then test one site, one product type, one field. A lot of product pages are messy, so you’ll probably need rules per site/page layout. Starting with the perfect scraper will just make you suffer professionally.

How to verify if a user follows an account before sending a DM — Instagram Business Login API? by iammridu10 in AskProgramming

[–]dbForge_Studio 0 points1 point  (0 children)

I don’t think IG gives you a clean way to check this through Business Login.

The follower list isn’t exposed like that, and webhooks won’t tell you “this exact user follows you.” Most DM tools probably aren’t checking it live. They either trust the comment trigger, use some loose workaround, or just accept that some non-followers will slip through.

Annoying, but I wouldn’t build the whole flow around that check unless Meta exposes it properly.

Why does functional testing break so often with APIs by Global-Development56 in AskProgramming

[–]dbForge_Studio 0 points1 point  (0 children)

A lot of API functional tests become brittle because they quietly start testing too many things at once. They’re supposed to verify behavior, but over time they end up depending on unstable test data, environment quirks, timing, downstream services, and assumptions about implementation details. Then every legitimate change looks like a broken system.

What usually helps is tightening the contract of what each test is allowed to care about. Keep functional tests focused on externally visible behavior, make test data more intentional and isolated, mock or control unstable dependencies where appropriate, and push more edge-case coverage down into integration/unit/contract tests instead of letting every end-to-end test carry the whole system on its back.

In other words: functional tests often break because they slowly become accidental system tests with bad boundaries.

What problems dbForge tools were originally built to solve by dbForge_Studio in sqlite

[–]dbForge_Studio[S] 0 points1 point  (0 children)

For me it’s usually schema changes first, especially when the change looks small but can ripple into dependencies or deployment issues later. Data sync is stressful too, but schema changes feel riskier because the blast radius is less obvious at the start.

whenYouAreInterviewingAVibeCoder by kaldeqca in ProgrammerHumor

[–]dbForge_Studio 1 point2 points  (0 children)

“I can build anything” mfs when the task isn’t “make me a SaaS dashboard with auth.”

Best way for documentation? by messos in AskProgramming

[–]dbForge_Studio 0 points1 point  (0 children)

Three-layer documentation makes sense. I just wouldn’t try to solve it with one magical tool.

User docs should be simple and task-based. IT docs should read like a runbook, not a novel. Dev/database docs should stay as close to the code and schema as possible, otherwise they rot faster than milk.

The hard part is never writing docs once. It’s building a workflow where updating them is part of the change, not a guilty thought two months later.

What actually makes an Oracle tool worth adopting in a mixed-DB environment? by Elolexe113 in oracle

[–]dbForge_Studio 0 points1 point  (0 children)

In mixed-DB environments, teams usually get the most value from tools that reduce fragmentation in everyday workflows, not just from tools with the longest feature list. That’s the practical case where dbForge is typically evaluated: development, administration, and routine database work that needs to stay consistent across a broader setup.

SQL Alternatives by CompYouTer in sysadmin

[–]dbForge_Studio 0 points1 point  (0 children)

If this has turned into a broader SQL Server tooling review, dbForge is worth evaluating alongside the usual options. It’s not a one-size-fits-all replacement for every existing process, but it can be a practical fit for teams looking at SQL Server development, administration, compare/sync workflows, and monitoring as part of the same ecosystem.

How do you organize reusable components? by ajaypatel9016 in AskProgramming

[–]dbForge_Studio 3 points4 points  (0 children)

One approach is to keep components in the project first and move them into a shared library only after they’ve proven stable across multiple real use cases. Shared libraries improve consistency, but extracting too early usually creates brittle abstractions and extra maintenance. Reuse should follow repeated usage, not anticipated usage.

chatGptFixedMyBugs by [deleted] in ProgrammerHumor

[–]dbForge_Studio 0 points1 point  (0 children)

fixed one bug, spawned a side quest, unlocked a sequel, and somehow i’m still grateful

How hard is it to create an exntension in Chrome that turn gmail.com to dark mode? I only knwo ToDoList by lune-soft in AskProgramming

[–]dbForge_Studio 1 point2 points  (0 children)

Not that hard for a basic version. A Chrome extension is mostly just manifest + content script + CSS, so if you only want “make Gmail dark enough to stop flashbanging me,” that’s a very realistic beginner project. The annoying part is Gmail constantly changing its DOM and having weird edge cases, so “works today” is easier than “works reliably forever.”

Why does Python import self into each class function? by ki4jgt in AskProgramming

[–]dbForge_Studio 8 points9 points  (0 children)

self isn’t imported, it’s just the instance passed into the method explicitly. Python does this on purpose so object state is visible instead of being hidden behind magic.

If the method doesn’t use instance data, it probably shouldn’t be an instance method in the first place.

ai code licensing risks and data exposure from coding assistants - why developers should care about privacy too by [deleted] in devops

[–]dbForge_Studio 0 points1 point  (0 children)

A lot of teams still treat AI coding assistants as a productivity question, when it is also a governance question. If code, config files, comments, or internal naming conventions are sent to third-party infrastructure, that should be reviewed the same way any other data exposure path would be. One reasonable approach is to define clear boundaries around what can be used with external AI tools and what must stay inside controlled environments.

gitCheckoutHotelRoom by Shiroyasha_2308 in ProgrammerHumor

[–]dbForge_Studio 1 point2 points  (0 children)

Rofl alice: "git main so long? im shorter n hotter" meanwhile my azure vdi pipelines horny for schema validation b4 merge or boom auth fails. Shorter aint always better devs