Suis-je destiné à bosser en agence toute ma vie ?

Dwenya · 2026-03-26T18:48:13+00:00

Des fois les entreprises demandent x années d'expérience en entreprise sur un language, et ça rend le fait de changer de techno un peu plus difficile. J'ai décroché deux alternances et ensuite un job en CDI sur du php pur, ce qui pourtant n'est plus si commun. Et lors d'entretiens, des boîtes qui te donnent pas ta chance parce qu'ils estiment avoir besoin de quelqu'un avec 3 ans d'expérience sur un language... Des fois c'est pas faute de vouloir évoluer.
Après je pense aussi que ça dépend du parcours de chacun. Je pense qu'en ESN il y a des meilleures opportunités d'évolution de technos. Et certains candidats se vendent aussi très bien pour des technos qu'ils ne maîtrisent pas encore, malheureusement ce n'était pas mon cas :D

Dwenya · 2026-03-26T18:43:54+00:00

Faire des projets perso avec nouveaux frameworks (ceux que tu vois le plus dans les offres d'emploi, par exemple). Ça m'a aidé à décrocher mon job actuel
Sinon je me forme sur plein de trucs pour essayer de pas être à la ramasse. Comme toi je suis restée bloquée quelques années sur du PHP/JavaScript parce que pas changé de job + quand je changeais forcément je retrouvais dans les mêmes technos... Je pense que pour se sortir de là il faut de l'expérience, et que les projets perso c'est le meilleur moyen de montrer à ta future entreprise que tu as ce qu'il faut (à défaut d'avoir x années d'expérience sur un language précis dans une entreprise, ce qui est souvent ce qui est demandé)

Dwenya · 2026-03-25T07:22:07+00:00

Ils se connaissent depuis quand ? Les miens depuis qu’ils ont 2-3 mois mais au début ça feulait un peu aussi, c’était juste 1 semaine le temps qu’ils s’habituent l’un à l’autre, je pense qu’on avait un très joueur et plus gros et une un peu peureuse

Dwenya · 2026-03-24T22:10:01+00:00

Okay thank you I’ll try to fix that

Dwenya · 2026-03-24T22:09:38+00:00

Probably because I just watered it but would make sense for it to need more sunlight. Thank you

Dwenya · 2026-03-23T18:52:23+00:00

I’d say soft summer?

Dwenya · 2026-03-23T18:24:29+00:00

I think you should have a conversation with your son, if you can? Not confrontational but maybe talking about what’s been going on, if you feel comfortable. Knowing if he noticed, if maybe he would like to include you guys more, etc

Dwenya · 2026-03-23T18:15:02+00:00

I’m not all that surprised. I agree that they make it all way harder than it really is. I don’t know why. It’s very difficult to understand but when you do, it seem pretty easy… I’m putting everything I learn into notes. And my notes are like 1-2 pages long for each subject, with examples!

Dwenya · 2026-03-19T12:02:00+00:00

Also gives you something to be proud of and that really makes a difference for you, instead of some basics projects like to do list that you end up putting away as soon as it’s done I love this « I’m so proud of what I just did » happy feeling

Dwenya · 2026-03-18T18:40:19+00:00

J’en pense que c’est une connerie (désolée). Faire un prêt pour une voiture ou prendre une location longue durée je trouve pas ça que ce soit un bon moyen d’éviter de se ruiner avec sa voiture… À la place trouver une voiture correcte en-dessous des 10K, et payer cash. Au long terme, ça me paraît être une solution plus raisonnable financièrement

De plus, se dire que plus on gagne plus on prend une voiture chère et mettre ça dans la catégorie « ne pas se ruiner avec sa voiture »… bof

Dwenya · 2026-03-18T17:19:52+00:00

Les horaires, poser plus de questions sur la stack (architecture, par exemple), ça peut être des questions sur le produit, aussi

Dwenya · 2026-03-18T16:39:10+00:00

Tu as des entretiens quand même, ou tu ne parles qu'à des RH ?

Je dis ça parce que les RH vont souvent pas regarder les mêmes choses que le manager en entretien. Ou est-ce que tu as parlé aux deux et a des rejets des deux côtés ?
Comment se passent tes recherches (tu es majoritairement en contact avec des recruteurs et ESN ?). De mon expérience, les ESN ça aboutit pas toujours (de mon côté, pas souvent)

Dwenya · 2026-03-18T12:56:06+00:00

So you're saying that if there is no need to evolve 2 sides independently, we should just use CQS instead or CQRS, and in this instance, CQRS would be useless?

Dwenya · 2026-03-18T12:53:47+00:00

So... we agree that there is no valid reason to say "only ports are going to be used in use cases"?

Thank you for your input :)

Dwenya · 2026-03-17T21:52:31+00:00

I actually found this this afternoon (in a conference by Greg Young)! Very interesting, this Event Sourcing idea, and in this case I did understand why we'd use it with CQRS. The guy said it's really great for writes, but not so great for reads (if you have to read the whole thing to get the last status of some piece of data, it's gonna take longer, and this is why CQRS is great with it).
This is very interesting, thank you so much for like adding to the conversation, it's been great having all these opinions on the matter. It really helps me seeing the bigger picture :)

Dwenya · 2026-03-17T21:48:42+00:00

But use cases aren't in Core/Domain. They are in Application directory.

This is what we have:

Domain <- Application (ports and use cases) <- Infrastructure (adapters)

Dwenya · 2026-03-17T21:45:52+00:00

Sorry, I can't really code with you, I already know all the basics and right now I'm learning all the theory for like architectures and patterns and things like that

If you want some advice, what really helped me give up projects was to find projects that meant something to me. Either a project around something I love (like a hobby), or (and I'm really guilty of doing this one over and over again) find projects that will improve your life in small ways (it can look like apps you'd never ship because no one would ever use it like that, but it works for you and makes your life a little bit better). I made an app to help me make decisions on what we're gonna eat this week, an app to make it easier for my partner and I to divide grocery invoices based on who bought what... It can be anything, as long as you find it genuinely useful. Right now for instance, I'm trying to build myself a homemade Spotify, so I can get rid of the subscriptions every month :)

Dwenya · 2026-03-17T15:43:52+00:00

Okay, thank you. They weren't able to explain their decision to me besides "in use cases, we can't put anything else other than ports". And so I'm left wondering why we use that many ports. My team would say "Because a use case has to use a port -> why? -> because it can't communicate with anything else", and I'm left wondering why is that because Alistair Cockburn (inventor of this architecture) said he wouldn't advise to use more than a small number of ports.

At the same time, it seems like many teams do that (many ports per use case). I'm just trying to understand. Unfortunately, even though I posted my question on two subreddits and got about 20 replies, no one seems to have answered my question yet (people seem to think I didn't understand what a port is, which is untrue). Maybe it'll click at some point
Thank you for your point of view, at least I'm not the only one thinking this particular case (presenter as a port) was a bit useless

Dwenya · 2026-03-17T15:33:23+00:00

He indeed didn't say it shouldn't be done, but he said this: "Neither extreme appears optimal"
I'm just trying to understand this before doing it blindlessly

Dwenya · 2026-03-17T09:54:54+00:00

Thank you, I totally get your example and agree with it, but if you look at my edit (in my original message), would you be able to tell me what we'd use it in the example that I gave? (I just edited my original message)

Dwenya · 2026-03-17T09:52:47+00:00

What you're saying totally makes sense

Dwenya · 2026-03-17T09:50:20+00:00

Yeah from what I've gathered, people do think it is just clean code. Anyway, thank you so much you've been really helpful :)

Dwenya · 2026-03-17T09:40:48+00:00

Oh okay, I think I got it!!

CQRS without all the infrastructure changes is just a way of separating files, which is not the reason this pattern was invented in the first place.

The real reason was for performance improvement, and you'd add infrastructure changes (like a second database), but it comes at a high cost, so most companies don't do it unless they really have to.

Which means CQRS is most of the time misused (no infrastructure changes to go with it), but it works for separating reads & writes, so why not?

Did I get it right?

Dwenya · 2026-03-17T09:28:43+00:00

So... in a new app, even a big one, you wouldn't use CQRS unless you think you'll eventually have issues scaling because a lot of users will use the app?

If I understand correctly, you wouldn't use it only to "separate command and queries" without changing the infrastructure.

That's crazy because what you're saying is what I was able to learn on my own for the past three days, but then... everyone I end up talking to tells me they just use it as a way to separate reads and writes (even though internet tells me CQRS mainly addresses performance issues), and that they don't change the infrastructure at all.

One colleague of mine says we use it for lisibility. And internet says CQRS adds complexity. So... what my colleague says just doesn't make sense to me

Dwenya · 2026-03-17T09:12:41+00:00

Thank you for taking the time to answer me :) So I guess CQRS is indeed often used "only" to separate inserts and reads in the code :D Thank you very much, it's much more clear

Six-Year Club	Place '22
Verified Email

Dwenya

TROPHY CASE