Code is just instructions, so ... yeah humans can totally be replaced with something more efficient & better... but what does 'better' really mean? is the output lower latency? higher concurrency? did it do something amazing with little resources?
I've only been in the industry 20yr, but I've met a wide range of people with different goals that drive many factors of many outcomes; as long as people are in the picture stuff is going to be inefficient from 1 pov, while at the same time human diversity can be a huge pool of talent/skill/creativity that a code generator can't have by design (it's solving for efficiency).
It would be a mistake to think things are never going to change. I think it's more reasonable to plan for change and try to keep a head of it by being relevant in a field that interests you, and has demand.
From your link: "Infrared light may cause damage to eyes in very intense concentrations, but it is highly unlikely that this would occur in everyday life. If you are working in close proximity to infrared lasers, wear the appropriate safety glasses or take appropriate protection measures."
The tiny LED on the front of the iPhone is nowhere near what you'd expect from industrial infrared lasers. I'm not sure the article makes the case that the infrared light from tiny LEDs is harmful.
deep breaths, and try to chill. when you need help, simply say "I need help" and that should be a trigger for someone to change context and actually help you, if they can.
not asking for help is the biggest mistake you could make.
Agreed. I once joined an engineering team as junior engineer at the same time they brought in a new principal engineer. He had lots of experience, but not on this specific project, so we were both on equal footing regarding the project itself.
I noticed the big difference between me and him was that he was very good at asking questions, whereas I fumbled around and tried to figure things out on my own.
Sometimes figuring it out on your own is exactly the right thing to do. But sometimes -- and especially now, as the newcomer in the group -- asking questions may be a better strategy.
- doesn't solve the problem
- adds unneeded/unwanted complexity (excessive ops for cleverness)
kinda like the DOM structure & bad CSS on the webpage... why is the side nav in the header, yet has a min-height of 1000px? what happens when the screen is taller? :)
practice like a pro athlete. the common belief that you need 10k hours to master something is imo, applicable to a 10x dev. when you hit 10k, if it's only during work hours you've likely mastered whatever mattered to your manager/org in that time frame, but that is not always transferrable or valuable to a new manager/org; practice is though.
practice creates experience, and if you have the resolve to push yourself out of your comfort zone and learn to master new areas, you should find yourself able to do things quicker than people that aren't familiar with the problem domains, easily attaining a 10x output while not creating problems.
Some cities were wood, and they burned. My concrete condo is in the burn path of the 'great Ottawa fire'. Wikipedia doesn't have enough pictures, worth googling.
I'm wondering if 'total collapse of cell walls and the complete densification of the natural wood with highly aligned cellulose nanofibres.' means that stuff isn't going to burn until you get temperatures where steel melts anyway?
> Massive wood walls and structural beams and columns comprised of engineered panels have demonstrated fire performance equal to concrete and, in some cases, superior to steel
one big difference seems to be that once the critical point is reached, even if the threshold very high, the wood contributes to the fire and nourishes it, unlike concrete or steal. a skyscraper with proper sprinkling should be fine.
Tons of major cities have been wiped out from fire in the early 1900's. But you have to consider how ill-equipped they were to handle fire, not to mention a total lack of research. Modern cities have working fire hydrants and buildings can have multiple fire suppression systems. Most of this is due to those massive fires happening.
Seconding this. My degree comes in handy all the time conceptualizing software and architecture problems into computer science problems, which are much less murky to solve. My practical experience comes in handy all the time with the day-to-day usage of libraries and frameworks, and "hands-on" skills ie debugging, deploying, etc.
I've only been in the industry 20yr, but I've met a wide range of people with different goals that drive many factors of many outcomes; as long as people are in the picture stuff is going to be inefficient from 1 pov, while at the same time human diversity can be a huge pool of talent/skill/creativity that a code generator can't have by design (it's solving for efficiency).
It would be a mistake to think things are never going to change. I think it's more reasonable to plan for change and try to keep a head of it by being relevant in a field that interests you, and has demand.