sterex

So?

This happens quite a bit even now. Many corporate Microsoft technology developers have a myopic view of the software world. This is on a downward trend, but still exists.

I understand what you are trying to say, but the movie ticket prices had sky rocketed beyond reach of a large section of the population. Now, you may argue that it is somehow the loss of the multiplexes by alienating people, but movies are somewhat of a necessity for cultural and social reasons.

Imagine having a consortium of telecom companies deciding to charge $100/Gb of data (assuming they are making profit nevertheless). There is no incentive for them to reduce the price.

To give you an example, a movie ticket would cost upto $20 in an economy where a bottle of water costs ~$0.2.

Is there a technical reason why it generates text with lot of spelling mistakes?

Ayn Rand seems very sloppy with her spelling!

Somehow I was hoping this was open source.

Please define "free".

This isn't really a tricky question who understands how JS works. If a person has not experienced this situation of a function call (closures) within a loop, I'd suspect he has not much practical experience.

It's much more difficult to understand this theoretically than when encounter this while you code.

Having used loopback version 2, moving to version 3 was relatively easy. I don't think it will be the same from 3 to 4.

Introducing MVC architecture is good - I'm yet to go through the code, but I'm guessing this will be inline with how Laravel is built.

But, why TypeScript? This seems like a strange decision to me.

Perhaps decoupling the <$.#> as (# x 0.01) would solve the problem right?

Not sure if that's what they do, but it isn't very complex.

Curious - Does CA have such a reputation?

Ideally, a man in his position should not leave his statements to such a wide range of interpretations.

Wow! I like it.

I liked the disclaimer on your github readme. :)

It would seem odd if the marketing checklist had "Create product", wouldn't it? :)

True! Also like one commenter said on the original article, if I have to share a file with 3 users, I will have to upload it 3 times and also there's the case of failed downloads.

Not sure if this is viable.

If it's very hard, you write or message it to them.

I agree. If your provider goes down you need to literally change your email and inform everyone and change it in all your services. If you own the domain, you can just switch providers.

How can a corporation like Google that handles Peta bytes of data on a daily basis say it is too hard for them to keep track of their own employee payments?

If they were honest enough, they would have found a way to comply. This is just their attempt at lawyering out of the situation.

I tried it and it works just fine. Changes from WSL(vim) and windows IDE were picked up correctly by nodemon.

JS is the new PHP! Yaay! :)

This actually makes sense. If the company thinks you are really needed, they will pay more for you. The bidding may go high, but it will only go as high as how much it would cost to hire an American instead. This would be a win-win because the under-qualified get filtered and the good ones get paid on par.

I worked on legacy code in my initial years. And when I say legacy, it was truly legacy. COBOL/JCL/REXX on a mainframe.

I now develop web apps using NodeJS and occasionally build UI using Angular and get to evaluate some of the "shiny-est", "cutting-edge" code/frameworks.

Do I think I wasted my initial years? NO. I worked on side projects which eventually helped me move to the tech I've always wanted to work on.

Did I do a shitty job on the legacy code? NO. On the contrary, I won many accolades for automating several processes and improving the performance.

Did I learn anything from working on legacy code? YES. A lot. I believe the experience of working on legacy code made me a much better developer.

Why do I think so? Working on legacy code means you READ more code than you WRITE. I am of the opinion that there are 2 things that are very difficult in software :

1. Reading code written by others. 2. Writing code that can be easily read by others.

Coding is one-time read, many-time read activity.

So, my advise - work on the code, stay in touch with what you like, but move if it's really bad. (No point in doing what you don't enjoy doing).

Just remember, the code that you write today will become legacy code one day. :)

P.S.: Also, beware of taking advice from a comment from a stranger on the Internet. :)

Could we not crowd source the captioning? I know I would help.

Very true. There could be socio-cultural reason as well. If a movie hurt the sentiment of a particular section of the society, you can expect 1-star ratings even from people who weren't going to watch the movie anyway.

Actually, Netflix is poised in a better position to filter between people who just rated the item vs people rating it AFTER viewing it (for a minimum duration). The latter class of people will have have more weight attached to their voting.

Yikes! They'd probably bury me if I used COBOL!

Exactly! The above comment assumes that a linter will be run against the core on the white board. Jeez.

Wow. That's pretty good. But how viable is it for them?

Yes. There are. There will be a cap on the maximum transaction that can be done using cash. So cash accumulation gets reduced. And hoarding large amounts of cash in physical notes will be dissuaded.

Right. But you know, it's a nice feeling. Even if it brings 0.000008% of joy. :)