Key Lessons Every Developer Should Know Before Taking Their First Freelance Client

·1 views

A software developer has shared practical insights drawn from personal freelancing experience, highlighting common pitfalls that go beyond technical work. The author emphasizes that a strong client proposal should define project scope, phases, and deliverables clearly — not just list a price — to prevent misunderstandings and scope creep. Approaching local businesses requires a tailored pitch, often including tangible demos, since unlike platform clients they may not yet recognize their need for a developer. Administrative details such as payment terms, communication tools, and ownership rights should be documented early, as skipping them frequently leads to disputes later. The developer also notes that reusing patterns and systems across projects builds speed and confidence over time, making each client engagement a long-term investment in one's own toolkit.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

How Layered DDoS Protection and Rate Limiting Defend Modern Web Apps

DDoS attacks overwhelm systems with fake traffic across multiple vectors, including volumetric floods, protocol exploits, application-layer HTTP attacks, and credential stuffing targeting auth endpoints. A layered defense strategy combines CDN scrubbing centers, Web Application Firewalls, API gateways, and application-level rate limiting to filter threats before they reach core services. Rate limiting rules can be tuned per endpoint — for example, capping login attempts at five per 15 minutes per IP, with CAPTCHA triggers and temporary blocks for repeated failures. Distinguishing bots from legitimate users relies on signals such as request rate, user-agent strings, TLS fingerprints, and JavaScript execution capability. While tools like Cloudflare and AWS Shield automate much of this protection, overly aggressive rules risk blocking real users, and sophisticated application-layer attacks that mimic human behavior remain difficult to counter.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

New Tool Automates NAP Consistency Checks Between Google Business Profiles and Websites

A developer has built an open-source Apify Actor called Google Maps NAP Consistency Checker to automate auditing of local business listings. The tool compares a business's Google Business Profile details — name, address, and phone number — against information found on its own website, a common pain point in local SEO work. It fetches up to two pages per business, uses regex and string matching rather than AI, and respects robots.txt rules before scraping any content. Businesses without independent websites are skipped at no cost, and the tool supports both US and Japanese phone and postal code formats. A built-in change-tracking feature flags previously mismatched listings as 'FIXED' on subsequent runs, giving SEO professionals a verifiable audit trail for clients.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Beginner Developer Shares First Python Project to Get Community Feedback

A Python beginner has built a student performance evaluator program as a hands-on exercise to apply newly learned concepts. The program calculates average marks across three subjects, evaluates academic performance using conditional logic, and independently assesses attendance. The developer intentionally kept academic performance and attendance as separate decision systems to avoid misleading combined outputs. The project has been shared on GitHub, with the author seeking feedback from experienced developers on code structure, logic, and readability. The exercise also led the developer to reflect that writing effective Python requires sound logical thinking, not just correct syntax.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

7 Silent Ways Scheduled Automation Jobs Fake Success With Exit Code 0

A developer running 30 scheduled automation jobs on a single Windows machine discovered that every failure over three months had falsely reported success, with the task scheduler consistently showing exit code 0. Root causes included a VBScript launcher discarding return values, a batch file where an echo command overwrote the real exit code, and a Flask service crashing silently at startup because pythonw.exe lacks a usable stdout stream. Windows Task Scheduler's default settings also caused silent failures, as jobs were quietly skipped or killed when the laptop ran on battery or when the user interacted with the machine. The developer's key takeaway is that exit codes alone are unreliable indicators of job success, and teams should instead verify that expected output artifacts were actually produced. Each failure mode required a targeted fix at its specific layer, from correcting VBScript syntax to overriding Task Scheduler's power and idle defaults.

0 comments Read more at DEV Community