you're right - it's kinda funny that boot camps are promoted because "university is a terrible way to learn programming", but they then try and sell boot camps as an effective way to learn the framework de jour.
Maybe if you finished an undergrad you'd be well equipped to stay on top of an ever-changing tech landscape?
well all those courses that aren't comp sci are still part of a degree, still require learning skills and still promote university-level thinking and production.
I think bootcamps actually demand a far higher rate of output and often at a very high level within specializations. The problem is I don't want to hire someone who can crank out bleeding edge framework code 20 hrs/day for 6 months.
what you are arguing is the captured surplus under the supply curve. We can assume that demand is essentially inelastic for a relatively large price range (hence the introduction of rent control) so the extracted value is the area under a curve that changes rapidly over the short term, or a less volatile curve that shifts out 7% every year. I don't see how either of you can be confident in the expected future actuals.
you didn't have to make that response before the law, as a hot market that drove up rates by 15% could be addressed shortly. If you loose the option to make quick upward decisions and any downward movement is essentially irreversible, game theory suggests you'll try to minimize how much increase you leave on the table.
Anyone else remember CD Now? Human-curated lists based on "if you like this you might like". Because they were actual people who loved and knew music they worked. Amazon wrecked that too.
Very good point. The best developer I ever worked with said to me one time "I'm thoroughly unemployable", meaning his skills, motivations and long term goals did not match what-so-ever with those of a employee developer.
He was a great resource but hiring him permanently would be a terrible mistake for all parties.
What about focus on direct referrals who have worked with a current employee? The highest signaling characteristic I've ever found is someone who was recommended by a former coworker; there's a transitive relationship that seems to capture both the technical skills and a comfortable fit.
I realize this doesn't scale to the rapid growth of some companies, but most of us need a more modest supply of talent vs. giant pools of people.
This is a good question because all the manufacturers are totally integrated; It's really hard to determine "where a car is made" because of parts and sub-assembly.
That said, several of the car sites tally up the origin of the parts and assembly and calculate the percentage (likely on a value-added basis) to determine "domestic content":
Well first a Tacoma is actually a truck; even Honda states the ridgeline is not intended to compete with traditional trucks, is not built for towing and uses a unibody construction.
Tacomas are expensive, the dealers don't deal and they hold their resale value. The new (2019) Tacoma trades heavily on it's reputation IMO, without really adding much new over the past 3-4 years. It's a real off-road vehicle though, if that's important to you.
In this format/size I'd suggest you take a look at the new Ranger. It's nothing fancy but much more affordable. It's pretty much the polar opposite of the Ridgeline.
>> However, it's easier to spend money than to sweat and suffer
not disagreeing with anything you're saying, however at the super-elite level everyone puts in the maximum amount of perfectly allocated effort into training and preparation. if we could eliminate 4 watts of drive train friction loss that would be material. For your average weekend warrior the points you make are definitely true, but hey, not the worst thing to blow your money on...
Good point. I don't think many would bemoan the loss of a bar, but they should recognize that losing a place other than home or work could have dramatic and far reaching impact.
In addition to churches I'd add the death of social organizations like elks, shriners, etc. Most of the good things these groups worked on are now seen by most as the responsibility of the government, which changes a lot of the dynamics.
Except you still have all those great options you mention (I played AoE II earlier tonight, in HD!) plus the excellent indie scene, plus you get all the blockbusters 9-12 months after release for a fraction of full retail. You've also got all those discount console games for PS and xbox (if that's your thing) and Zelda on switch is amazing.
Stay away from the pay to play, most sports titles and anything on casual mobile and you've got it better than ever before. And it all runs on a decent windows PC that's less than 7 or 8 years old.
Well, I'm an engineering manager and there's a little more to then someone just taking 10 sick days per year. I see when my direct reports are run down or if they're fighting something, versus if they're always "sick" on Monday morning. I known when they stay home because they don't want to get everyone else sick but they are still in contact; that's different from when they call in sick, I hear nothing all day and then they're fine the next day and back at work. I keep a tally of when someone who's never sick is really down for an entire week vs. those who consistently get "food poisoning". The whole reason I have a job is because we're a tight-knit team that works closely and there's no room to bullshit. It would be like faking out your parents when you're a kid; you could get away with it for a day or two but I'm going to be able to tell when you just want to stay home to play video games.
I don't think this makes me passive-aggressive or a shitty manager; we're a tight team that cares about each other and as a result we know when people are treating each other with respect and honesty. I give people a lot of leeway and ask them not to wreck it for everyone. If someone threatens this it makes me both mad and sad, because once it's gone we'll never get it back.
This is a sign of a mature developer who gives previous devs the benefit of the doubt: they probably weren't idiots who didn't care. As a development manager now I often push the benefits of consistency and targeted, localized improvement against the attitude of this sucks and is all garbage.
This entire post sounds like it was written by an alien trying to compress a full theoretical understanding of the bicycle into an essay without ever having ridden one. super-weird tone to the whole thing; they discount many researched aspects of bicycles and present the information like it's brand new.
Maybe if you finished an undergrad you'd be well equipped to stay on top of an ever-changing tech landscape?