> I see clouds in the sky, and green grass. It has been fifty years and I am sitting in the park with my dog, feeding ducks and watching the local children at play. I haven’t uttered the phrase “type-safety” in years. All the startups are gone. I am free.
MV arises naturally. You can run the entire application logic without UI components, and you can test it that way also.
Other abstractions are designed similarly to allow tests against pieces of the internal API in total isolation, though separated on different lines. Maybe you have transient state stored in view models while persisted state is stored in models. The isolation only helps as size grows, and it can keep size under control mostly by having a good data model for what each component / layer / aspect actually does.
It makes it easier to rewire everything when you start with a switchboard. UI changes are either "Oh my god we're going to have to re-write so much stuff if we do it that way!" and you wind up not making drastic UI changes or "Sure, we can make that thing tickle the controller instead of that other thing."
Newton's method and other numerical methods are the hello world of machine learning.
Why numerical methods?
* They might produce the right answer
* They frequently do
* They are easy to visualize or imagine
* You get used to working with a routine that is both fallible but quite simple and remarkably able to work in a wide variety of situations. This is what machine learning does, but there are more sophisticated routines.
At some point you need to make a decision to go down the road more focused on analysis & modelling vs machine learning & prediction. It's not that the two are exclusive, but they really do seek to address really big forks in the problem space of using a computer to eat up data and -- give me predictions or give me correct answers
Google needs lots of prediction to fill in holes where no data may ever exists. Analysis and modeling can really fall down when there is no data to confirm a hypothesis or regress against.
An engineer needs a really good model or the helium tank in the Falcon 9 will explode one time in twenty vs one time in a trillion. The model can predict, based on the simulation of the range of parameters that will slip through QA, how many tanks will explode. Most prediction methods are not trying to solve problems like this and provide little guidance on how to set up the model.
On the prediction side, you will learn all the neural net and SVM stuff.
On the analysis and modelling side, get ready for tons of probability and Monte Carlo stuff.
> Newton's method and other numerical methods are the hello world of machine learning.
Newton's method and other similar numerical methods are the hello world of a branch of mathematics known as 'numerical analysis' and scientific computing. This is not Machine Learning.
Librarians often don't realize that they can't keep plugging in method bodies and get what they want forever. Engineering isn't f&@!ing Madlibs for Christ's sake. Learn to build things that will work 100% of the time and never compromise!
People talking about getting ink need to focus a little more on the underlying issue, the gas-lighting of greedy "founders". My employment contract & bonus contract had to all be walked out on as it was all predicated on my CEO being trustworthy. I recently met up with several other employees who didn't get paid for the end of their contracts either. The thing we liked most about talking was figuring out it definitely wasn't our problem.
> If the author's reading this, it sounds like you're fairly early in your career and learned a tough business lesson the hard way
Yeah. Second that. Experience is good. Knowing what it all actually looks like, the phrases, the mannerisms, is very valuable. You can take bigger risks when you know how the terrain rolls.
As an example of my senses getting more developed, recently I talked to a "CEO" of some startup I was interviewing and asked about someone else I liked who I knew at the company from earlier. Check this out:
"Oh, yeah [person] is really great...blah blah blah."
"So how is [person] doing?"
"Oh, well, they decided they wanted to do something else...blah blah blah."
Complete total waste of time was brewing if I didn't probe into the non-specific answer that artfully implied that [person] hadn't left the company and was soon part of my awesome team. I would have at the least researched them more. When you have to waste time on things like this, it makes getting where you want to be way harder and makes it harder to justify risks.
"My employment contract & bonus contract had to all be walked out on as it was all predicated on my CEO being trustworthy."
In what way was it predicated on your CEO? A CEO can't simply decide to not honour a written and signed legal document, without risking a court case (the onus is on you to go after what is rightfully yours).
Learning to navigate human interaction in business (and make no mistake, a employee/employer relationship is a business transaction) is a skill needed in any industry. These kinds of things are not new, in this industry or any other.
Unless you have a large pot of money to spend on litigation (or the amount of the contract falls inside the limit for small claims), all contracts amount to trust. The cost of fighting a legal battle is enormous, and mid-sized to large businesses can fight battles of attrition in court.
Indeed, unless substantial amounts of money from a client who can pay are involved (think Brian Reid (!) who was let go from Google 9 days before their IPO because he was too old: https://en.wikipedia.org/wiki/Brian_Reid_(computer_scientist... ), contracts only serve to memorialize decision and promises, they help avoid "but I thought you meant X" retrospective flaky human memory.
The optics were horrible, it sounds like he had a fairly strong case, and for those of us who knew of him starting from his works like Scribe way way back when, well, we're inclined to believe his story.
All we know is that Google made an offer he and his lawyer chose not to refuse, but as long as they thought they were going to win in court before a jury and all that, it had to have been generous, although I'd imagine it wasn't as generous as his original ability to to participate in the IPO and beyond.
They can lie about having the means to fulfill the contract or any basis to pay damages etc. CEO is a good job to lie from. You can always complain that your employees should have made you filthy rich so that you could fulfill your promises.
One reason I quit was that all of the mounting promises were predicated on me in the end. If that's true, go alone instead of giving yourself bread through a middle-man.
