https://www.telegraph.co.uk/news/worldnews/northamerica/usa/...
579 karma · joined January 23, 2015
https://www.telegraph.co.uk/news/worldnews/northamerica/usa/...
I started getting errors while pushing, only then I realized that there is some outage
remote: Unexpected system error after push was received.
remote: These changes may not be reflected on github.com!
Even the website is not available.So suppose you have the following pseudo code:
x = f()
In other languages you start using 'x' straight away. You can call member functions on it, compare it, etc.
In Rust if x happens to be of type Option or Result (which are wrapper types i.e. they wrap the value), then you need to understand these first very well to write idiomatic Rust code. These types have combinator functions like 'map', 'and', 'and_then', 'or', 'or_else', 'unwrap_else', etc. if unwrap() is not suitable for your use case. If you are coming from a non-functional language, one cannot help get a feeling that all you wanted was to use the value and you have to learn so much upfront. At the end of it you are mentally exhausted.My productivity increased a lot, once I realized that there is a pattern to these and knowledge gain with Option & Result is transferrable to using Future's combinators as well. It is very hard to explain it to someone as to how to get to this state. There lies the challenge with teaching Rust and I think Steve Klabnik and team has done really good job with documentation.
Now there is a failure crate https://github.com/withoutboats/failure. It is an improvement, but it still feels that one has to type a lot for something basic. Now, this is a matter of taste and many people will be ok with this.
Life-cycle of a Rust developer: https://imgur.com/kNkV7jm
Good, bad and the ugly: https://imgur.com/udNcZXa
With Go, in my head it is best explained in terms of the scene in the movie: Pursuit of Happyness
Boss: Chris. What would you say if a guy walked in for an interview, without a shirt on, and I hired him? What would you say?
Chris Gardner: He must have had on some really nice pants.
People (including me) find lot of issues with Go in terms of some choices in the language. But boy it does have some really nice pants and that is the ease of writing networking services + Go routines
Nice to see front page example using 'impl', the recent most improvement in ergonomics. Before 1.26 things would be different. This makes me more appreciative of the efforts from Rust team/community to improve the ease of use.
Offcourse, one can argue that the 3rd party Rust libraries can use a lot of "unsafe" code which we as consumer may not know about. But the situation is still better than C++.
I have learned the hard way that one needs to spread out the achievements. For example if you have good number of ideas then don't spew out all of them in one go. Introduce them say in each quarter and people will say "Joe always seems to have an idea round the corner". Recency effect matters.
This led to one more question. Do driverless cars have (or will have) a black box like that of aeroplane?
Tools like bors act as a "force-multiplier".
Jenkins does allow 'parallel' jobs but that is the same thing we want.
Baby boomers say lot of first things getting unfold in front of them e.g Humans going to moon, Nuclear tech, Electronics, Mass entertainment (Television), etc. These are the legacy of that generation. Many of things they simply couldn't have guessed the consequences of their actions.
The same thing applies to the current generation. What will be our legacy? One of the things is increasing removal of human beings from the equation using AI, automation, etc. We do not know fully how this is going to affect future generations. If things get screwed-up the next generation will blame us.
Suggestion: could also cover closures (which would demonstrate the move keyword also)
2. "This too shall pass", https://en.wikipedia.org/wiki/This_too_shall_pass Nothing is permanent, the good days and the bad days
Recent activities on this:
Note ban (Nov 2016) => https://en.wikipedia.org/wiki/Indian_black_money#Ban_on_1000...
Using analytics (today's news) => http://economictimes.indiatimes.com/news/economy/policy/i-t-...
Official site:
https://swachhbharat.mygov.in/
Dashboard: http://sbm.gov.in/sbmdashboard/
1) Iteration: We get to practice our stuff on real entities (language, OS, databases, etc). Do architects get to "practice" actual work at their home? Do new doctors get to try experimental surgeries? Do amateur civil engineers get to build those iconic bridges? They can do computer simulation ... but it is actually a software.
2) Hackathon: Can't imagine this happening in say medical field, mechanical engineering, law etc. Software Industry is one of few industries where this can be done.
3) Changing the world quietly: Many in my relatives are not programmers. It is hard to explain to them in what ways software is changing the world.
4) Open source: Imagine Coca Cola sharing its secret recipe. It won't but we as SE get to learn from open source projects. Now there is a cultural aspect to this but the point is that we as SE can experience it more than other professions.
Sure there are more things to add (like identifying key interfaces) as others have mentioned here. This is a nice starting point though.