Skip to main content
7 events
when toggle format what by license comment
Oct 22, 2021 at 18:27 comment added Kam ok thank you I’m there.
Oct 22, 2021 at 18:25 comment added Sarov Let us continue this discussion in chat.
Oct 22, 2021 at 18:24 comment added Kam I’m not going to argue because I used to work at big tech firms and what you are saying is the norm. In this case, can you assume that what I’m saying is correct please. Front End and Data Engineering is very orthogonal at lease in this team and they won’t be able to make any meaningful contribution. It took my DEs 6 months to understand data concepts, it not that simple. My question really becomes in this situation: should I treat Front End and Backend Engineering as fungible and 1 team from planning perspective and follow your strategy and treat data engineering as a separate team?
Oct 22, 2021 at 18:16 comment added Kam My front end engineers are front end specialists, they can’t possibly work on the data layer, that requires years of training they don’t have nor want to get.
Oct 22, 2021 at 18:13 comment added Kam You’re saying: if there’s an abundant of backend work the front end folks can assist so things smooth out (and the team estimations would be fairly accurate). I’m saying that front end folks can’t actually assist backend folks. So things won’t smooth out.
Oct 22, 2021 at 16:28 comment added Kam Well the issue is that my team isn’t fungible. The FE folks can’t possibly work on the database.
Oct 22, 2021 at 16:23 history answered Sarov CC BY-SA 4.0