vemv

53 ms·

541.
by vemv 10y ago
he could attemp to reuse the password in other websites
542.
by vemv 10y ago
no-op point is true (except for logged out users - then the check is still useful) Anyway, how do you consistently decide to which 10% you show the new feature? That piece of data is better stores in your Users table, as I see it. Plays wel
543.
by vemv 10y ago
Haven't tried it myself, but why not use authorization libraries instead of specialized 'toggle' libraries? After all, both are concered with whether user X is allowed to do Y. Using just one approach might be a clean, mainta
544.
by vemv 10y ago
Just learn to use argumentation.
545.
by vemv 11y ago
Where's your reasoning? Homebrew gave theirs. Keep in mind that no personal info is ever sent. Just a random UUID.
546.
by vemv 11y ago
Here's the PR for that https://github.com/atom/tree-view/pull/804/files
547.
by vemv 11y ago
Language performance rarely impacts web applications performance. Actual bottlenecks are the database, and your webserver/architectural choices.
548.
by vemv 11y ago
> Does anyone else have this experience and do you think it's reasonable to request the company you work for to provide a nap time? Yes, definitely. Word it as an extended lunch time though. Also, remark your productivity boost, whi
549.
by vemv 11y ago
Normally you get a lunch pause which can take anything between 30-120 minutes. Up to you how long the pause takes, later you have to compensate obviously. I often have been the only guy at the office who took naps at lunch time.
550.
by vemv 11y ago
Rails freelancer here. The first thing that surprises me is that the author talks about 'wasting' time, which is 'his precious resource'. How is that? The more you work, the more you bill, if you got any decent deal with
551.
by vemv 11y ago
My original wording was too concise, sorry.
552.
by vemv 11y ago
Designing an infrastructure which allows you to solve problems by firing up more instances is non-trivial work, beyond the skillset of many (otherwise apt) developers.
553.
by vemv 11y ago
Obviously no technology will give you infinite horizontal scaling for any sufficiently complex app. There is more than one way to achieve scalability. Microservices is just one of the possible choices. It annoys me that developers increasin
554.
by vemv 11y ago
Becoming encumbered by a monolithic centralized API that is at risk of reaching its maximum performance and hosting limits. Comically wrong. You can just fire up more instances (aka horizontal scaling). Microservices have their merits, bu
555.
by vemv 11y ago
I guess your point being that these aren't novel techniques? The author sure didn't invent them, but they aren't widespread enough yet. In fact e.g. Rails puts you in the opposite mindset (which is OK at early stages).
556.
by vemv 11y ago
I retract my opinion - the approach is clearly correct for that business domain. The key difference is here: > The thinking is that if a client is shopping for a class in a different timezone, why would we convert the class's time t
557.
by vemv 11y ago
Seems a misguided practice to me. * Store datetime values in UTC. Else you get inconsistent values, which has unpredictable consequences. * Detect user's expected timezone using one of : a) user preference setting, b) the region the ap
558.
by vemv 11y ago
Are up-to-date Rails applications exposed to this issue? Not 100% sure, but from what I know, Rails gets timezone handling right. Specifically, it leverages the https://github.com/tzinfo/tzinfo gem. So, correct me if I
559.
by vemv 11y ago
> Not even leading indentation on blank lines. Ugh. I wonder how is this a real issue? Non-indented blank lines ARE an issue though - they make code editing more cumbersome, requiring pressing the tab key far more often. Also, tabs are f
560.
by vemv 11y ago
On the micro level, you're right. On the macro level, the new generations of smart talented folks are choosing CS over other career choices.
561.
by vemv 11y ago
Workers are a must for any minimally sophisticated web application. You cannot degrade HTTP response time (and whole app server performance) just because you are performing work synchronously before the request finishes. Similarly, if the w
562.
by vemv 11y ago
That's entirely true. But maybe those startups which 'changed their tune' didn't have to worry about servers for N months, focusing in e.g. market fit and growth hacking instead. Lean Startup mode. Personally I'm pr
563.
by vemv 11y ago
The same thing that prevents so many developers from using Docker: it's not a drop-in miraculous infrastructure simplifier. It may pay off for certain organisations, but it currently a quite a rabbit-hole, with a constantly changing la
564.
by vemv 11y ago
A sophisticated crowdfunding-based service for a particular niche.
565.
by vemv 11y ago
One sure can have a DO droplet for a minimal rate, but unlike Heroku/AWS, they don't offer anything oriented to high availabilty, resilience, auto-scaling, performance (via workers), etc.
566.
by vemv 11y ago
Dividing your architecture into separate components is not only needed for operating at scale (the "nice" problem to have), but for having high availability (or even decent performance) at all. Depending on one's business, HA
567.
by vemv 11y ago
It's called Elastic Beanstalk! As it name suggests you can start as easily as with Heroku, and adapt it later with whatever additional AWS infrastructure you may need.
568.
by vemv 11y ago
Really? Do men-in-the-middle matter if your communications are encrypted (be it HTTPS, PGP)?
569.
Pay per use – the missing trend(medium.com)
3 points by vemv 11y ago|0 comments
570.
by vemv 11y ago
The tampering issue is described in the article.

More ›