Yeah and, for sure, it won't pass... considering how conservative we are, plus the legal side of the proposal is not so clear in where the money will come from.
1,873 karma · joined September 3, 2014
Yeah and, for sure, it won't pass... considering how conservative we are, plus the legal side of the proposal is not so clear in where the money will come from.
I traveled some times from Zürich to Munich and saw that in the German side, rails have no electricity and then the SBB are forced to use a diesel powered machine, but except for that, I still have to find a connection where the diesel machine is necessary every time, I am curious!
The Silicon Valley situation is more visible for the simple reason that diversity is still a problem, so having so few girls makes this a huge problem and a barrier hard to overcome for women. I feel truly sorry for all the female colleagues having troubles with bosses and colleagues harassing or also bullying them (have you ever heard somebody saying: "she's a girl, let's give her this task b/c is very trivial").
So I created this small utility that gives the opportunity to select just a small portion of the main screen that is later available to be fullscreen on a secondary screen.
Anyway, NoSQL is definitely a good solution for some usages, I personally created a special analytics service using Cassandra that is good to store unstructured and unrelated data to be later computed and analyzed. It would be barely impossible to achieve this without hitting on performances due to the data integrity checks that most SQL servers/engines perform. On the other hand, I use SQL everywhere else and I am happy with that. It scales well if the design is well made and it's just a matter of research and a little bit of preparation to create an SQL environment that scales. It's not easy as some NoSQL databases, but not that hard and impossible as some of these solutions are claiming to gain new customers...
On Node.js I have some doubts, even if the general nature is very scalable and is well proved as fact, there are other solutions that are good alternatives like Golang or some frameworks written in Scala, maybe on top of AKKA.
The big problem is that a lot of companies and investors are asking for scalability, but the reality is just that one service on hundreds built are going to be so successful to require a scalability plan. If you hit that target you would definitely get enough money to even migrate the technology to something better and scalable.
I have a similar product (different domain) of the second pitch, I never had any kind of these questions. Most of questions in Europe were about intellectual property, patents, rights, defensive strategy against competitors and similar. I noticed a big difference between the mindset of an American investor compared to an European one, incredible.
Anyway, I think SpaceX's engineers are extremely under pressure right now. These missions are extremely risky, everybody knows how difficult is this field and I personally believe that the amount of pressure the team is facing, it's consistently increasing the potential risk of a failure.
SpaceX is a private company and, like all the other private companies in the earth, it has the goal to make money and make investors happy. Every single failure of the company is a big hit on the brand and a loss of millions and millions of dollars, this put the team under an excessive amount of pressure.
> A website — graphics, content, visual elements — is copyrighted at the time of development. So putting the copyright notice on the bottom of a site states that the material displayed is not to be used without permission of the owner. In fact, you don’t even need the notice to claim copyright; the law eliminated the requirement of public notice in 1989.
Source: http://www.sitepoint.com/what-it-means-to-copyright-a-websit...
The environment is not friendly, it's getting better, but I can't consider it genuinely equal. In the opposite I think the way she's trying to pursuit the goal is wrong and counterproductive. There are many other ways to achieve a goal like promoting gender equality in tech scene, fighting with insults and expose (barely) fundamentalist opinions on Twitter would not help.
I posted it because it shows how bad is this and how it has gone far from by being a simple "contrast of opinions". One of the 2 guys involved posted this online, I think this deserves to be discussed and explained.
I don't like to post private conversations, but this has been reported in other communities and it is an important piece of the puzzle to crearly understand the situation.
This has to be discussed, because I think we need to fix the gender gap, but this kind of "fundamentalism" is not healthy. This doesn't seem to be the right path, but maybe I could be wrong.
This is very interesting, this means there's a big business behind it. I don't know which are the requirements to be hired as prison guard, for sure is, as you said, an unpleasant and dangerous work, but I don't get why a prison guard should be paid higher than a cop, that is always facing criminals, but in more dangerous situations.
> Several years ago a Federal judge ordered the state to reduce prison overcrowding. It hasn't made much progress.
This would definitely cost a lot, prison overcrowding, in some countries, is a big issue. There's no real solution other than build new prisons, hire new people and transfer prisoners. I read in the past an article stating that the future of prisons will be mostly private, turned into a real business. I honestly laughed in a first instance, then reading a lot about the topic, I figured out that maybe that article wasn't so much wrong after all...
I had a small collection since a couple of years ago composed by Sun Ultra-60, Next Workstation (working, but original HD was gone), Next Cube (never worked), Commodore 64, Sinclair ZX Spectrum, Apple Macintosh (not working) and some others machines people were not interested anymore and I was able to collect for free. It was a quite good collection and funny to deal with in the spare time, but then, one day, my father decided to discard all of them because they were old and mostly broken. I was so disappointed it took me a while to realize it.
Whats the potential outcome of this? I am not an expert about this kind of things in the US, but in Europe this would mean an invalidation (if any violation is proved) of the job contract. So the guy basically loses the job pretty much immediately and gets probably fined.
I hope he will get caught if he's involved and that his face will disappear forever from the football world. That sport is amazing, but in the last (almost) 20 years, it has been ruled by a man with a dubious integrity.
I was actually thinking about go Elixir-first, but I was in a need of a kind of "validation" about the order from someone that already wrote some code for both.
Let's see how I can formulate my thoughts about Swift without say something that can be considered trivial.
I think Swift can be basically resumed with this quote:
> Crucially, the vast majority of this is incidental complexity, not essential complexity.
I love Swift, I think is a good language, but is far away from perfection. Sometimes I feel that is half-baked compared to languages like Scala. I can understand the complexity and the obstacles that are part of a development of a new programming language, but some things are really messy.
I truly hate these 3 factors:
> enum cases act like functions, but are not functions.
> Properties act like functions, but are not functions.
> Initializers act like functions, but are not functions.
Plus the fact the language is not homoiconic freaks me out, sometimes.
I like Swift because constantly challenges my skills as engineer, I have to find workarounds to apply all the concepts I know about functional programming, but... this is the current feeling, I don't know if in a long run this would persist, I can't image to fight against the language like I have to do sometimes, would make me still happy in 2-3 years, maybe some day I would get tired.
I like Swift, there's a lot to do to jump from a good language, to an awesome language, but now we are still far away from that.
This makes feel the project more interesting, because if I hit one of the already covered problems, I already know where I can (probably) find the solution.