r/devworld

5000 applications, hundreds of rejections, 1 offer — my honest experience breaking into tech
🔥 Hot ▲ 74 r/devworld+10 crossposts

5000 applications, hundreds of rejections, 1 offer — my honest experience breaking into tech

Shit,

I dont know how to start this. I spent ungodly number of hours applying for jobs for few years. Had couple of interviews which led me on but never returned back or it was full of rejections. The number crossed more than 5000. I know job market sucks but there is always a hope guys dont give up.

I made a video on how i started, what I did, my experiences, my mistakes during the applications to help some of you out the best I can. If you guys would love a watch here is the video

https://youtu.be/RRGOAj2dEX4?si=hA4Z37JryRJoIYXx

Comment if you guys had similar experiences as me I am also open to help you guys out in your search journey

Thanks

u/Beneficial_Pie_7169 — 9 hours ago
▲ 24 r/devworld+5 crossposts

I almost ignored a huge user signal.

I built an AI tool for games. It was working. Users were active. I was heads down improving it.

But I kept seeing characters and animations that didn't belong.
• A sweaty broccoli floret for a workout app.
• A neon octopus for a multi-agent AI tool.
• A tiny, armored armadillo for a password manager.

These weren't game makers. These were app builders.

They were hacking my game tool for something completely different. They wanted their brands to stand out and their users to feel something.

My first instinct? That’s not what this is for.
But the signal didn't stop. So I leaned in. Talked to them. Understood the problem.
No one could find a fast, affordable way to get a professional animated mascot.

So I also launched what they asked for.

u/missEves — 16 hours ago

The build thread is open - who's shipping something?

A new week just started. Make it count.

  • One line on what you're building and who it's for
  • Link it if it's live, real eyes, real backlinks
  • Take 2 minutes to check out someone else's project too

Drop it below. Someone here needs exactly what you're building. 👇

reddit.com
u/BriefNzoni — 4 days ago
▲ 3 r/devworld+2 crossposts

SaltSnap is live - Salt to Taste Calculator

Guys THIS is why I wanted to make apps. Not to make a ton of money - I'm still at a loss with my LLC and insurance costs. Not to find problems and solve them. But to solve the problems I've had for years as a person managing a household, and have been surprised nobody tried it sooner.

Salt to taste is the most overused instruction in cooking. Its fine in gravy and dishes where you salt at the end. It has no place on raw potatoes, raw chicken, in a casserole before it hits the oven. I have 372 recipes in Plan to Eat (shoutout) and 1/3 of them say Salt to Taste.

I've wanted to build a calculator for years, but it seemed like too much input each time (ingredients, weights). Now that AI can scan a recipe for you, it was time.

SaltSnap uses a calculator created by me (a 40yo mom who's become a very good cook) using all the science/best practices and refined using 100s of recipes. When a user scans a recipe and gives feedback, that feedback is used to further refine the calculator.

Please check it out and lmk what you think. https://apps.apple.com/us/app/saltsnap-recipe-seasoning/id6762474072
Promo is no my thing (mom, FT job, busy) so if you have any tips I'd very much appreciate it.

u/RComish — 10 hours ago

Is building things (personal projects) in programming worth it?

I read a book about the LSM tree and got to know about it. It explains the concepts and how it works (may be a little bit high level, but it doesn't tell the implementation. Honestly, it is overwhelming for me, and I didn't know where to start. So, I decided to take a small chunk of it and started learning AVL tree first. This is my progress. Right now, I'm stuck at AVL tree.

My thought is this. I may be able to build only a working LSM tree (if I'm consistent enough to finish the project), and there will be hidden errors. Implementation will be wrong. And no one will use it, and it'll just sit in the corner of my GitHub after I finish the project. The only value I see is that I will be familiar with the programming language I use (I'm planning to use Golang). Plus, the fact that I have a working LSM tree.

Honestly, I'm unable to continue because I'm not sure it is worth it.

What are your thoughts? Any help is appreciated. Thank you for your time.

reddit.com
u/DevShin101 — 4 days ago

Dormant account handling logic in new platforms: is it just an operational efficiency issue?

Recently, there has been a recurring pattern among emerging platforms where, upon transitioning accounts to a dormant state, access to user assets becomes excessively restricted. This appears to go beyond simple database cost optimization and may reflect a system design choice aimed at reducing short-term liability ratios by effectively freezing liquid assets.

In standard practice, a more balanced approach involves segmenting grace periods and providing dedicated withdrawal channels, allowing platforms to maintain both operational efficiency and user trust. Within the analytical framework of Oncastudy, have you encountered cases where dormant account policies were used in a way that effectively restricted or reclaimed user assets under questionable conditions?

reddit.com
u/rootznetwork — 2 days ago
▲ 6 r/devworld+1 crossposts

Have you ever seen a system stay “healthy” but the timing between events starts drifting?

I’ve been running some simple timestamp tests on event streams and noticed something interesting.

In a few cases:

no errors

no thresholds crossed

everything still looks “healthy”

…but the spacing between events starts to:

widen slightly

tighten slightly

or trend in one direction

Example output looked like:

“Rhythm looks healthy but spacing is widening slightly.”

Individually it’s subtle, but it’s clearly not the original pattern anymore.

Curious how you all think about this:

Do you treat that as noise until something breaks,

or do you consider that an early signal worth acting on?

u/RedLINEGuardian — 4 days ago

[Hiring] Remote Developers Wanted – Build Real, Impactful Software Solutions

We’re looking for experienced developers who want to focus on creating and shipping high-quality software, not just sitting through endless meetings.

If you enjoy writing clean code, solving practical problems, and delivering features that matter, this role is for you.

What you’ll do:

Develop and maintain software applications

Build new features and improve existing systems

Debug issues and optimize performance

Work with APIs, databases, and third-party integrations

Collaborate on enhancing product functionality and reliability

What we’re looking for:

Strong experience in software development

Proficiency in one or more programming languages (JavaScript, Python, Java, PHP, C#, etc.)

Understanding of APIs, databases, and software architecture

Ability to work independently in a remote setup

What we offer:

Fully remote (Prefer EU/US/CA)

Flexible, part-time friendly schedule

$21–$43/hour based on experience

Work on meaningful, real-world projects

Interested? Send a message with your location 📍

reddit.com
u/OrchidAlternative401 — 6 days ago

[Hiring] [Hybrid] - Frontend Developer – Large E-commerce Marketplace Platform | Japan, Tokyo

Our client is a leading e-commerce marketplace platform in Japan, offering one of the largest online shopping experiences in the country. They provide a platform that connects millions of shoppers with thousands of merchants, focusing on high-quality user experience, scalability, and innovation in online commerce.

We are looking for a proactive Frontend Engineer with experience in JavaScript, HTML, CSS, and React/Node.js, strong skills in performance, architecture, testing, and security, who can collaborate effectively, take ownership, and drive solutions for a large-scale e-commerce platform.

Responsibilities

  • Defined requirements, designed, developed, tested, and deployed frontend features for a large-scale e-commerce platform
  • Collaborated with product managers, backend engineers, and cross-functional teams
  • Monitored system stability and performance, and implemented performance optimizations
  • Improved frontend architecture through refactoring and code optimization
  • Troubleshot production issues and ensured high system reliability

Technologies

  • JavaScript, HTML, CSS
  • React.js / Node.js
  • Git
  • Unit testing (Jest or similar frameworks)

Key Skills

  • Frontend performance optimization
  • Web security best practices
  • System design and architecture
  • Unit and integration testing
  • Collaboration in an international engineering environment

Job Level

Middle/Senior

Senior (at least around 7 year+ of professional experience or the equivalent skills)

Mandatory Qualifications:

- Development experience with JS, HTML, CSS for more than 3 years (ideally more than 7 years)

- Development experience with React.js or Node.js

- Deep understanding of frontend performance optimization

- Knowledge of Web security

- Experience of system design

- Experience of testing (Unit Test, Integration Test)

- Communication skill in English     

Desired Qualifications:

- Experience with ESLint

- Experience with unit testing implementation in JavaScript (Jest, Intern, WDIO)

- Ability to design front-end architecture

- DevOps experience

- Experience of Git

- Always act in active way and lead to the solution

 Languages

  • English: Fluent
  • Japanese: Optional / a plus

Work Environment

  • Fast-paced, dynamic global environment with collaborative teams across multiple locations

Salary: ¥6.5M – ¥11M JPY per year
Location: Hybrid (4 days in the office, 1 day remote)
Office Location: Tokyo, Japan
Working Hours: Flexible schedule with core hours from 11:00 AM to 3:00 PM
Visa Sponsorship: Available
Language Requirement: English only

Apply now or contact us for further information:
Aleksey.kim@tg-hr.com

reddit.com
u/FunMuted6440 — 4 days ago

신생 플랫폼의 컬러 스키마가 체류 시간과 이탈률에 미치는 영향

특정 톤의 색상이 지배적인 신생 사이트에서 유독 사용자들의 체류 시간이 극단적으로 짧아지거나 특정 행동으로 쏠리는 현상이 관찰됩니다. 이는 시각적 자극이 뇌의 보상 체계나 불안 심리를 즉각적으로 자극하여 논리적 판단보다 본능적인 반응을 우선하게 만드는 구조적 특성 때문입니다. 실무에서는 이러한 심리적 편향을 억제하기 위해 보색 대비를 낮추고 시각적 피로도를 줄이는 중립적인 UI 가이드를 적용하여 사용자 신뢰도를 확보하곤 합니다. 여러분은 플랫폼의 메인 컬러가 데이터 수치상으로 유저의 의사 결정 속도에 유의미한 변화를 준 사례를 경험하신 적이 있나요?

reddit.com
u/rootznetwork — 3 days ago

[Hiring] Sales & Outreach Partner – Software, AI & Web (Commission)

We are a software development firm specializing in custom software, websites, and AI models trained specifically to user preferences. We also produce high-quality promotional ads for the products we build.

We are looking for an outreach partner to identify and secure new buyers.

Our Services: Software Development, Web Development, Bespoke AI Training, and Ad Production.

Compensation: Commission-based with a high, fixed percentage per deal.

The Role: Lead generation and client acquisition.

If you are a results-driven closer, DM us to discuss our portfolio and commission structure.

reddit.com
u/AccomplishedAge3648 — 5 days ago

InsAIts v4.8 released fixes false positives from v4.0–v4.7, adds AutoGen support and token optimization

InsAIts v4.8 False positives fixed, tokens saved, AutoGen supported

If your team installed InsAIts between version 4.0 and 4.7, I need to flag something

important: those versions had a set of false-positive detection bugs that have now

been fully resolved.

What was wrong:

In versions 4.0 through 4.7, five detectors could fire on perfectly normal agent

behaviour truncated output on short replies, context collapse on structured data

files, blank response misclassifications, over-aggressive action-intent gating, and

false PROMPT_MANIPULATION or SHADOW_SERVER alerts on legitimate requests. There was also a broken `python -m insa_its.collector` CLI entrypoint (FileNotFoundError) and a JSON crash on malformed hook payloads.

These issues meant some users were seeing alerts that shouldn't have been there, which undermines the core value proposition: trustworthy anomaly detection.

What v4.8 fixes and adds:

All five false-positive classes eliminated (FP1–FP5)

CLI entrypoint fully repaired

JSON crash on hook payload malformed input resolved

Token optimization: non-critical detectors demoted to doc-only mode, with

escalation gates that only fire when a pattern repeats within a window. In practice this means significantly fewer tokens consumed per session without losing any detection coverage that matters.

AutoGen / ag2 integration: `AutoGenMonitor` wraps `ConversableAgent` instance using the native `register_hook()` API. Supports two-agent chat and GroupChat.

Read-only hooks observe, never mutate.

Guardian session vault: task progress is captured as checkpoints, enabling session continuity without replaying full conversation history.

Update now:

```

pip install --upgrade insa-its

```

If you're running multi-agent pipelines in production and care about catching hallucination chains, jargon drift, uncertainty propagation, or tool poisoning this update matters. Don't run v4.0–v4.7 in prod any longer than you have to.

u/YUYbox — 18 hours ago