CitconWiki - User contributions [en]

Code until you die / older female devs

2025-09-27T16:44:55Z

Mstoy:

* enjoy building stuff - what does that look like as you get older? work less hours / higher ethical alignment
* what itch are you scratching by coding? just problem solving? not only, also the process of building
* ageism in interviewing? what happens if you are not needed anymore? open-source?
* invent ways to make coding more enjoyable when not depending on salary anymore
* crisis of identity - got into business because of joy of building stuff, no joy in pair programming / consulting / banking -> launch something yourself, be your own boss, no "external dependencies"
* career/coding break?
** early retirement, only occasional coding
** after first child: asked for 3d and got it, after 2nd child: stopped working 2y, missed it, hard to get back in with CV gap
* on average, awful management - dangerous: really good in one specific area, have not seen anything else
* getting older: worse memory, better at seeing bigger picture - need to find places where people care about that
* most contracts due to contacts to persons that work in decent places
* woman in tech: 20% of brain power used to deal with assumptions of other people
* Thoughtworks diversity commitee: nobody had family...
* quality of employees diluted to hit hiring targets - CTO: need representation in promotion panels
* need to put loads of processes in place to make job work, people become "blockers"
* role model for younger female devs
* FT had female leadership team
* on a team with younger female devs - how to make them stay / aid development?
** processes centered around males - address those
** double-check how you advertise jobs,
** don't try to hide the fact you are female just to fit in
* bringing babies to work helped with clients behaving
* what could help diversity?
** adapt expectations as people age (e.g. peri-menopausal brain fog)
** could you not replace with 20something new hires? hiring is not fair, but high representation of older devs in interview processes helps
* instigate cultural change at company level - people problem, how to instigate change? older people bring a voice of experience
* values in order: people, money, tech stack
* form a team with different strengths
* banks / big tech still have too much money, therefore hard to enforce better processes
* everybody cares about the projects that make the company the most money - more/better interaction with users
* is what you optimise for compatible with what the company optimises for? (exchange time for money)
* bonus schemes are counter-productive
* cognitive decline is inevitable, do we all need to switch roles before retirement? can fight it to an extent with eating/sleeping well etc
** part of satisfaction is being good at your job, what if that changes? -> definition of "good" changes over time
* code until you die? perhaps not as a paid developer, but many examples of paid programmers retiring with >60 years

Code until you die / older female devs

2025-09-27T16:41:33Z

Mstoy: Created page with "* enjoy building stuff - what does that look like as you get older? work less hours / higher ethical alignment * what itch are you scratching by coding? just problem solving?..."

CITCONEurope2025Sessions

2025-09-27T16:40:52Z

Mstoy:

{| class="wikitable"
|-
! Room
! 10:00 - 11:00
! 11:15 - 12:15
! 12:30 - 14:00 (Lunch)
! 14:00 - 15:00
! 15:15 - 16:15
! 16:30 - 17:30
|-
| Presentation Area (6th Floor)
|
|
|
|
|
|
|-
| Space 1 (7th Floor)
|
| [[What is CBT and how it can help you?]]
|
|
|
|
|-
| Space 2 (7th Floor)
| [[HardCoreGit]]
|
|
|
|
|
|-
| Space 3 (7th Floor)
|
|
|
|
|
| [[Code until you die / older female devs]]
|-
| Kaizen Room (7th Floor)
| [[How can we accelerate change adoption in users?]]
| [[Vibe Coding with Glamorous Toolkit]]
|
|
|
|
|}

HardCoreGit

2025-09-27T10:07:26Z

Mstoy: Created page with "* messiest git situation and how it was solved ** a while ago: project with sub modules 4 levels deep, not well supported at the time * when to use git submodules? ** e.g. w..."

* messiest git situation and how it was solved
** a while ago: project with sub modules 4 levels deep, not well supported at the time

* when to use git submodules?
** e.g. when depending on third party dependency code (googletest, zlib, ...)
** when 2 products use the same public interface - extract it into a submodule
** a submodule stores url, path, sha1 -> saves time when re-building

* git now supports sparse (partial) checkouts, filtered clone, large file storage (LFS)
** LFS helps where large binary files change a lot, "plain" git is already great for big files that don't change

* how to migrate from subversion to git when lots of deployment
** git tags?
** git describe relative to a tag - soft indicator of where in timeline you are
** timestamp of commit? - hard to get back to a specific commit from a given timestamp
** (not a sales pitch) consider getting external help, eficode has experience in this area

* pros and cons of monorepos
** split or not based on behaviour / branching strategy / verification
** is it good enough for what I need to do right now?

* cool git tricks that might be useful for the average user
** git diff filters to quickly see changes to checked in xls/zip/images... files (.gitattributes + .gitconfig section diff)
** git smudge filters, e.g. for dynamically changing line breaks to unix/windows, encrypting/decrypting sensitive data (also used for LFS)

CITCONEurope2025Sessions

2025-09-27T10:04:49Z

Mstoy:

CITCONEurope2025Sessions

2025-09-27T10:03:49Z

Mstoy:

CITCONEurope2025Sessions

2025-09-27T10:03:32Z

Mstoy:

CITCONEurope2025Sessions

2025-09-27T10:03:08Z

Mstoy:

Markus Stoy

2025-09-27T09:03:22Z

Mstoy: Created page with "https://www.linkedin.com/in/markusstoy"

https://www.linkedin.com/in/markusstoy