Kind of doesn’t matter since it’s been since before phones were smart. But as a hiring manager it’s going to depend on the position you’re applying for.
Mostly backend: need to have a load testable API with session management and security. Avoid using an ORM so you can display your master of SQL. Mostly front end: solid and stable client the exemplifies everything you know, cookie management, CSRF protection, rebuilt in multiple frameworks to show that you can work with the big ones. Mobile? Same thing. Balanced? Well you already built all the features so you should be fine.
Good luck, the market is pretty rough for now, but it will get better eventually.
Avoid using an ORM so you can display your master of SQL.
I’d probably still ORM, but with targeted performance optimization queries does in raw SQL so you show not only you can handle both, but also understand the limitations of ORMs.
I’d also maybe throw in some explicit error handling to show if you lose connection things don’t just spin forever, crash, or just show “Error, something went wrong”. I see lots of fairly nice UIs until something goes wrong, the server times out or whatever and the app completely shits itself.
Generally, show understanding of the topics not just how to use them. I’ve seen so many promising developers get completely stuck once the real world hits and it’s not exactly how they’ve been taught.
Kind of doesn’t matter since it’s been since before phones were smart. But as a hiring manager it’s going to depend on the position you’re applying for.
Mostly backend: need to have a load testable API with session management and security. Avoid using an ORM so you can display your master of SQL. Mostly front end: solid and stable client the exemplifies everything you know, cookie management, CSRF protection, rebuilt in multiple frameworks to show that you can work with the big ones. Mobile? Same thing. Balanced? Well you already built all the features so you should be fine.
Good luck, the market is pretty rough for now, but it will get better eventually.
I’d probably still ORM, but with targeted performance optimization queries does in raw SQL so you show not only you can handle both, but also understand the limitations of ORMs.
I’d also maybe throw in some explicit error handling to show if you lose connection things don’t just spin forever, crash, or just show “Error, something went wrong”. I see lots of fairly nice UIs until something goes wrong, the server times out or whatever and the app completely shits itself.
Generally, show understanding of the topics not just how to use them. I’ve seen so many promising developers get completely stuck once the real world hits and it’s not exactly how they’ve been taught.