public inbox for gdbadmin@sourceware.org
help / color / mirror / Atom feed
From: "Mohamed from Mohamed’s Substack" <zaysann@substack.com>
To: gdbadmin@sourceware.org
Subject: The Struggles of a Young Developer
Date: Wed, 15 Nov 2023 02:47:10 +0000	[thread overview]
Message-ID: <20231115024710.3.b9f0a8a2c9603716@mg2.substack.com> (raw)
In-Reply-To: <post-138879306@substack.com>

[-- Attachment #1: Type: text/plain, Size: 1467 bytes --]

View this post on the web at https://zaysann.substack.com/p/the-struggles-of-a-young-developer

This is an almost-true story about a young passionate developer. It was the late 2004 and he had just started working in a small company offering everything he desired: a good salary, working with his preferred programming language, approaching complexities, and modeling architectures.
This was not the first working experience of the young developer. But his very first project had proven to be problematic. At the time he believed features would never change. But he was wrong, and every feature change would require a complete refactoring, causing bugs and an enormous wasting of time. He had tried even some virtuous approaches like writing tests. But his tests required maintenance, and time to be written, and even more time to be executed.

Unsubscribe https://substack.com/redirect/2/eyJlIjoiaHR0cHM6Ly96YXlzYW5uLnN1YnN0YWNrLmNvbS9hY3Rpb24vZGlzYWJsZV9lbWFpbD90b2tlbj1leUoxYzJWeVgybGtJam94T0RJek56UXlNRGdzSW5CdmMzUmZhV1FpT2pFek9EZzNPVE13Tml3aWFXRjBJam94TnpBd01ERTJORE16TENKbGVIQWlPakUzTURJMk1EZzBNek1zSW1semN5STZJbkIxWWkweU1ETTVNekkxSWl3aWMzVmlJam9pWkdsellXSnNaVjlsYldGcGJDSjkuWDJhQ2RwMHNROW5nd0NMa29CY3B5ZlV1aXdyRlBtMWtGMlY4b1RoUEQ3ZyZleHBpcmVzPTM2NWQiLCJwIjoxMzg4NzkzMDYsInMiOjIwMzkzMjUsImYiOnRydWUsInUiOjE4MjM3NDIwOCwiaWF0IjoxNzAwMDE2NDMzLCJleHAiOjE3MDI2MDg0MzMsImlzcyI6InB1Yi0wIiwic3ViIjoibGluay1yZWRpcmVjdCJ9.lpGK75rLonfPv0I5POfnElE_P0ATDfADvSd_BlF9GFs?

           reply	other threads:[~2023-11-15  2:47 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <post-138879306@substack.com>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20231115024710.3.b9f0a8a2c9603716@mg2.substack.com \
    --to=zaysann@substack.com \
    --cc=gdbadmin@sourceware.org \
    --cc=reply+2aonyi&30kwu8&&caced21fdae7fbf54ed1cae942c0bb00dc15a3411c5890c54885c28c6df445a3@mg1.substack.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).