Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
I wonder if they'll ever do Bootcamps for any other engineering positions. I mean a Bootcamp Electrical Engineer would be absolutely comical, but I could honestly see there being something like Bootcamp for specific focuses. For degrees like electrical, where the items you learn about in school are often outdated, offering some sort of "What's New" per field (microelectronics, processor designs, fiber optics, quantum computing, etc) might actually be pretty useful.
I think a boot camp would be really useful for cobblers
Bazinga
I could see a networking bootcamp for electricians.
Full-stack boot camp devs - ideally you find a direction.
Be open to everything as a junior. But in your first three years, lean towards something specific and then be a master at it.
Be open to everything as a junior. But in your first three years, lean towards something specific
Do you mean pick a direction after three years? Cause < 3 years is junior (unless you're working at a consultancy giant meat grinder then that would be senior and close to retirement from consultancy).
Lean towards something specific, like farming corn, or busking with a hurdy-gurdy.
I started my career at a consultancy and after working in a myriad of other types of companies I'm back at working in a consultancy. The trick to work on an IT consulting company is to find one with ex-engineers at management.
It's been a breath of fresh air when you can have management back you up when dealing with client's bullshit. TBH in some cases it's also less stressful because your value to the company can be calculated much easily based on how much you're assigned in a project, so it's given me a lot of "fuel" to renegotiate my contract several times.
I think there's a cycle of consultants getting senior, being tired of the higher ups commission and starting their own little consulting company. This company is small, efficient and friendly for a while, but it grows because everyone wants more money or it is sold to someone else. So eventually it becomes another one of those meat grinders and the cycle continues.
I thought this was quite an insightful graphic until I realised the terms backend and frontend were borrowed from the terms back of house and front of house.
Is that really where they came from though?
So... too many cooks creating overly complicated meals that occasionally are admirably but more often then not are not worth the money. Also really hard to get into and make more efficient.
Bloated complex frontend with so gosh darn many tools, some specifically created for one certain meals but sometimes get used for other meals, more or less effective. Sometimes it's already at the table, sometimes gets delivered with your meal.
Fancy looking APIs but you somehow have to know how to correctly talk to them and if you phrase something wrong, well good luck.
VS:
Simple, efficient, maybe not as sophisticated but if you get too many customers: just order a second one.
You mean snaps? 😉