#2 weakest projects?π³π³π³
1 messages Β· Page 1 of 1 (latest)
maybe the second or fourth one
also if you keep the fourth one, it might be a good idea to not say "implemented layer caching to improve build efficiency by 30%" because you didn't implement layer caching, Docker did
and Docker's main selling point isn't improving build efficiency - it doesn't really do that
and maybe replace 'async hashing' with 'hashing' since the 'async' part is extraneous
Thanks mate
You can reorder the steps of the Docker file to make use of cached builds
Perhaps leveraged layer caching? Or something like that
I only really kept the MERN stack one because lots of people recommended having a general full stack app with modern tech. I personally donβt like it much
oh i see what you mean now, you properly made use of docker's layer caching
in my opinion i don't see much value in that because doing so doesn't really improve performance past a number that you would have ordinarily gotten without docker, it is just the way you do things to write a good docker file. but to each their own and i suppose it does show that you can write good dockerfiles
same thing with me lol - except i need to add some MERN-y stack on my resume. i think that feedback was out of bias of writing or doing so many things mongo or react that it didn't seem challenging. but i think my feedback was misplaced as u mentioned :P
I think having one MERN/MEAN stack is just good by default for most full stack/SWE positions (too lazy to tailor for every app)