The point of the post is to be mostly descriptive. I don’t see where you get the idea I’m trying to push any particular tech. I have not advised anyone to replace their web platform unless they have explicitly asked for it, and I think WordPress is an excellent choice. Using website builders is and has always been, a trade-off between user convenience and developer convenience, and if you work in this industry you know this. I think you’re reading far too much into what I’m reporting here. Also, I’ve worked as a full-stack web developer for 15+ years, at larger companies, startups, web agencies, and as a freelancer.
To clarify what I mean by system-level thinking:
Instead of thinking of every EA org as an isolated entity with isolated needs, I think of all of them as a collective. There is technical knowledge to be transferred between them and improvements that can be made to all organisations at once. For example, several organisations I’ve talked to have an interest in creating a job board, or improving the one they have. At the same time, I have also talked to 80,000 Hours about their plans for their job board and the fact they are hiring a director to run that specific project. This tells me there’s an opportunity for them to expand the functionality of their job board to a point where several of the other organisations don’t need one of their own. Maybe creating job boards for smaller organisations shouldn’t be a priority until it’s clear what’s happening with this popular, already existent job board.
I just think it’s a good idea to think about the needs of all EA organisations at once because there might also be solutions that allow meeting them for everyone while avoiding duplicating work.
The point of the post is to be mostly descriptive. I don’t see where you get the idea I’m trying to push any particular tech. I have not advised anyone to replace their web platform unless they have explicitly asked for it, and I think WordPress is an excellent choice. Using website builders is and has always been, a trade-off between user convenience and developer convenience, and if you work in this industry you know this. I think you’re reading far too much into what I’m reporting here. Also, I’ve worked as a full-stack web developer for 15+ years, at larger companies, startups, web agencies, and as a freelancer.
To clarify what I mean by system-level thinking:
Instead of thinking of every EA org as an isolated entity with isolated needs, I think of all of them as a collective. There is technical knowledge to be transferred between them and improvements that can be made to all organisations at once. For example, several organisations I’ve talked to have an interest in creating a job board, or improving the one they have. At the same time, I have also talked to 80,000 Hours about their plans for their job board and the fact they are hiring a director to run that specific project. This tells me there’s an opportunity for them to expand the functionality of their job board to a point where several of the other organisations don’t need one of their own. Maybe creating job boards for smaller organisations shouldn’t be a priority until it’s clear what’s happening with this popular, already existent job board.
I just think it’s a good idea to think about the needs of all EA organisations at once because there might also be solutions that allow meeting them for everyone while avoiding duplicating work.