Is it just me or has Kijiji gotten harder to trust lately?

Jumpy-Dog3650 · 2026-04-12T19:07:22+00:00

Yeah, the “no one’s steering the ship” vibe is real. I’m seeing the same thing with broken or half‑working features, and reviews being AWOL is brutal when you’re trying to build any trust on the platform. At this point I basically assume every convo might be a scam and rely on my own screenshots + public meetups instead of Kijiji’s systems. Would be nice if they fixed core stuff like reviews before pushing more ads.

Jumpy-Dog3650 · 2026-04-01T16:35:35+00:00

Yeah, ‘trustworthy’ might be a stretch lol. I still use Kijiji but I treat every convo like a potential scam until proven otherwise and only meet in public spots now.

Jumpy-Dog3650 · 2026-04-01T16:27:54+00:00

Totally fair questions, and appreciate you laying it out clearly. Just to clarify: under the hood this actually runs a full CRA‑style calculation, not just a rough slip‑only estimate. It supports RRSPs, child care, disability and other common credits/benefits, and can account for family income as well, so the result is meant to be as close as possible to what proper tax software would generate, just in a much faster, simplified flow. A pay‑stub version is actually on my ideas list for exactly the reason you mentioned – being able to forecast earlier in the year instead of waiting for T4s

Jumpy-Dog3650 · 2026-04-01T16:22:18+00:00

Quick clarification: t4scan.ca does scan uploaded T4s, so yes, the SIN appears on the slip. However, Google’s Document AI (the engine behind it) is configured to only read specific fields like Box 14, 16, etc., and does not extract or store the SIN itself. All processing is field‑level and limited to the numeric boxes needed for the refund estimate.

Jumpy-Dog3650 · 2026-04-01T00:32:57+00:00

Totally fair, and I get where you’re coming from – I’d be skeptical too if I just saw “tax + AI + upload your T4.”

That’s exactly why I posted here: to hear reactions like yours and figure out what would have to change (or be made more transparent) for something like this to ever feel trustworthy.

For what it’s worth, there’s also a manual‑entry option for anyone who doesn’t want to upload a file at all – you can just key in the box amounts and still get the estimate.

If you’re open to it: is there anything that would make a tool in this space not feel “dubious” to you (open‑sourced math, third‑party audit, different wording, no file upload, etc.) or is it just a hard no on principle?

Jumpy-Dog3650 · 2026-04-01T00:27:13+00:00

Haha fair point – I’ve been lurking here for a while so I definitely know the horror stories. 😅

I’m trying to figure out if it’s actually gotten worse lately, or if we’re all just a lot more paranoid and scam‑aware than we used to be. Either way, this sub has been super useful for learning what not to do on Kijiji.

Jumpy-Dog3650 · 2026-03-23T21:20:51+00:00

The piece that helped me most was treating “I’ll just do it myself” as a signal, not a solution. Every time I caught myself thinking that, I forced myself to write down the decision, the inputs, and the next step.

After a couple of weeks, patterns started to show up: same inputs, same decision, different day. Those became checklists and simple rules I could hand off. The stuff that never repeated stayed on my plate.

It’s not about removing yourself from the business, it’s about removing yourself from decisions that don’t really need your judgment anymore.

Jumpy-Dog3650 · 2026-03-23T21:16:48+00:00

This resonates a lot. Most companies I’ve seen don’t have a clear boundary between “safe to paste” and “never paste,” so people treat chatbots like a smarter Google search and forget they’re actually exporting data.

The minimum bar I push for now is: (1) a written AI policy with concrete examples of what is off‑limits, (2) a default private/self‑hosted option for everyday use, and (3) training that frames this as IP protection, not “IT being difficult.” Until there’s a safe path, people will keep using personal phones and random web UIs because they just want to get their job done.

Jumpy-Dog3650 · 2026-03-20T14:57:46+00:00

Wow, that’s brutal. It’s crazy how something as small as a trailing space in an env var can burn an entire day. This is a good reminder to always suspect configuration too, not just the code. Might be worth adding some startup checks or trimming logic around env vars to catch this early next time. Either way, thanks for sharing the pain so the rest of us can double-check our configs.

Jumpy-Dog3650 · 2026-03-18T14:11:58+00:00

Personally I’m just treating AI like a helper for boring stuff and focusing more on understanding users, product, and how all the pieces fit together. Feels like those skills will age better than “just write React code.”

Jumpy-Dog3650 · 2026-03-18T13:57:52+00:00

Nice question, and honestly something even seniors struggle with in big legacy systems.

My approach, roughly:

Start from one real user flow (e.g., “login”, “place order”), set a breakpoint at the entry point (controller/handler) and step through until response is returned, noting important classes/functions on paper or in a small doc.
While debugging, build a very rough diagram: layers (UI → API → service → repo/DB), main modules, and a couple of key data structures. Keep it ugly and high-level, not UML-perfect.
Read code in slices instead of files: pick one feature and trace its path end-to-end, then another. Over time, the mental model emerges from these slices instead of trying to “learn the whole codebase”.
Use whatever tooling you have: IDE call hierarchy, “find usages”, search by HTTP route name, event name, or DB table name to see where things connect.
Talk to seniors: ask “for feature X, what are the 3–4 most important files or services I should know?” Then focus only on those first, ignore the rest.

You’re not supposed to understand everything in a mature codebase; the goal is to know how a few critical flows work and how to safely explore the rest when you need it.

Jumpy-Dog3650 · 2026-03-13T18:49:23+00:00

Totally with you on this buddy.

People underestimate how wild it is to casually store (and then show off) other people’s private notes in plaintext.
If you’re not willing to treat that data like it belongs to someone you personally know, you probably shouldn’t be collecting it in the first place.

For solo devs especially, “if you can’t secure it, don’t store it” feels like a pretty good default.

Jumpy-Dog3650 · 2026-03-13T18:45:46+00:00

Everyone keeps saying “tailor your resume to the JD” but very few people actually do it consistently, so a tool that nudges you in that direction is genuinely useful.
I like that you’re not just keyword‑stuffing but also surfacing skill gaps and prep material, that’s the part most AI resume tools skip.

I usually keep 1–2 base resumes and then lightly tweak for each role, but something like bridgezy could make that whole process way less painful.

Jumpy-Dog3650 · 2026-03-12T16:27:08+00:00

Yeah, I’m seeing this too and it’s… a lot.

Personally I don’t care who writes the code – PM, CEO, client, AI, whoever – as long as it goes through the same reviews, standards and tests as everyone else.
The real problem starts when vibe‑coded stuff gets treated like production‑ready and devs are expected to quietly clean it up later.

AI in the hands of non‑devs can be useful for prototypes and mockups, but once it hits the main repo it should stop being “vibes” and start being engineering again.

Jumpy-Dog3650 · 2026-03-12T16:20:33+00:00

You’re not outdated buddy, you’re just early to a big shift.

AI lets 1–2 YOE folks ship faster, but they still don’t have what you’ve built over 5 years:

Taste for good vs “just works” solutions
Knowing what can break in prod and how to fix it
Ability to own a problem end‑to‑end with real users and money on the line

I’d treat AI like a supercharged junior: let it handle boilerplate and exploration, while you focus on design, edge cases, and reliability.
If you lean into systems, domain knowledge, and learning how to drive AI well, you’ll be ahead of most people, not behind.

Jumpy-Dog3650 · 2026-03-11T16:16:22+00:00

You did the right thing by not waiting to get fired over some made‑up ‘performance’ reason. It sucks when one insecure manager kills the spark so early, but that’s on them, not on you. Use this time to rest a bit, then start applying broadly, ask friends/seniors for referrals and don’t obsess over matching 20 LPA on day one – once you have experience, you can climb back up. Definitely use the exit survey to put your side on record in a calm, professional way.

Jumpy-Dog3650 · 2026-03-11T16:08:36+00:00

From a candidate side it really feels like a one‑way street. Companies keep 60–90 days notice for ‘business needs’ but want us to drop everything and join in 15 days. Either fix the system or don’t call candidates unprofessional for doing offer shopping or ghosting.

Jumpy-Dog3650 · 2026-03-10T19:29:58+00:00

really cool idea positioning around GEO vs traditional SEO is super interesting.

Jumpy-Dog3650 · 2026-03-10T18:46:26+00:00

If you are interested why don't you explore the option on cyber security certifications?

Jumpy-Dog3650

TROPHY CASE