We learn that our families aren't the same we see on our favorite TV shows. It hurts & its sad for young children to experience a struggle, but I think they can ultimately strengthen them -- unless the difficulties are so severe, or misguiding, that they lead children down the wrong path of life (i.e. severe psychology disorders, crime).
Again though, the world/nature is a tough place, and its nice to want to enforce being easier on and conceal realities from children, but I think there is something of value in experiencing "realness"/struggle -- a simple & less-harsh example is the losing team getting no trophy.
Personally, I feel as though they are getting out of hand. A guy in my org literally has 5 certs, and does very minimal AWS work (basic web product). I have no certs and am building out cloud native apps in AWS doing things like batch processing millions of customer data. I'm not knocking being able to learn and enhance your skillset and marketability... I just think something is fundamentally...
Wouldnt the approach for security updates be to replace the container?
"Find all the subsets in a set that add up to sum" -- "Okay for this we will use the sliding window technique and here is how it is done" -- WTF is this. I get that they want to see problem-solving skills, but this is on a different level requiring the interviewee to have studied and knowledge of the technique, otherwise we are basically trying to develop efficient algorithms from scratch and in little time. --This makes sense for college interviewees who have only studied the past 4 years, but for a professional with experience, why is this adequate??
Does algorithmic programming matter?-- still yes. But the way it is interviewed is absurd and inadequate. I had a production service centered around the stable-roommate-problem. It took me a week or two (mostly research) to develop something out and fit it into our codebase. It then took 1-3 more weeks to actually make it work for us and cover edge cases (i.e. Irving's algo quits after instability -- this isnt an option in the real-world). I read much material on the subject, other's code, had many deep-thinking sessions where I was mostly in my head, wrote unreadable scratch on paper, collab-whiteboarded (sometimes arguing), tested&failed PoCs, and had many breaks in-between it all. How successful was that project?--very, did I need to know and study techniques with lacking/meaningless basis to do it--no.
This is just a new industry competitor, correct? or am I missing something?
The success resulted from deep research and much trial & error. It was no magical "algorithmic skillset" that they expect in those type of interviews (I wonder if those are even a good filter for actual production algos).
Here is my simple write-up of SRP: https://medium.com/@rambossa/stable-matching-algorithm-and-h...
"Find all the subsets in a set that add up to sum" -- "Okay for this we will use the sliding window technique and here is how it is done" -- WTF is this. I get that they want to see problem-solving skills, but this is on a different level requiring the interviewee to have studied and knowledge of the technique, otherwise we are basically trying to develop efficient algorithms from scratch and in little time. --This makes sense for college interviewees who have only studied the past 4 years, but for a professional with experience why is this adequate??
btw the email stated it was for viewing "how to start a startup" lectures, not CS
I don't get why this is a red-flag though. Unless everywhere I've worked is highly flawed. Unforeseen production issues are a given, no? Like how do you actually mimic your IaaS?
I’m not trying to bring about a formal argument here and I may be way off, But IMO these type of quotes are borderline reflective of Marxism or wording that belong in Mein Kampf.
Everyone thinks that the main competitor for building communities is Facebook.com. But fbook.com does not build communities, they digitize existing ones.
So all these new apps come out with "better facebooks" not realizing (or accepting) that they already exist as Twitter, Reddit, and Instagram. These existing platforms are very good at true connection and community building.
How does "Hello" fit into that?
I can possibly see this being different if I didn't have a static position/desk and my mornings were consumed with meetings or high activity.
It's now 2018. Most hype and notable examples I saw with RN were around 2016 (https://facebook.github.io/react-native/showcase.html).What is the state of React Native today? How are you using it successfully, and at what scale? Any large applications that have fully implemented it?My success isn't beyond fast proofs-of-concepts or simple ux applications. Success for me is defined as a system...