827 karma · joined April 30, 2012
I will shed a single tear for grep though.
I have used this professionally for: - Detecting plagiarism in submitted works - Detecting languages of strings to catch translation issues
All technology is a tool, use the right tool for the job and move on.
I'd also make the assertion that the article fails to account for people like my co-workers, who are not millennials and use Car2Go more often than anyone else I know. Parking is absurdly expensive where I work, so people use Car2Go to avoid that. I used it to get to school until I was able to purchase a car of my own, at which point the costs shot down dramatically and I now have a secure asset -- as you pointed out. It made way more sense to own -- and still does. Perhaps as these businesses grow, they will be able to rival the prices of ownership and offset the downsides of not having a secure asset. If that happens, I will certainly reconsider owning.
That being said, I do feel that a lot more people in my generation are less inclined to desire a thing because of the status it assigns you. Perhaps I'm just an out of touch dreamer though.
I would support you.
... But I do like watching videos on my Apple TV.
In a browser, the TCP connection will close itself. On a mobile device, the TCP connection will close when the network connection drops.
I suppose a server could reliably keep a TCP connection open, but at that point why wouldn't I just deal with the messages myself..?
My initial concern is connection stability issues. What happens if the client's connection drops out for a period of time? Do clients have to explicitly leave the channel?
My team was estimating a story recently which could have used this, but we didn't want to spend the time and effort to build a whole infrastructure for one message. This would have been perfect! If I find some time, I'll give it a try and send you my feedback.
I'll definitely look into this tool, thanks.
- You say it is HTTPS over a persistent TCP connection, does this mean I can make standard HTTP request... Like using xhr from JavaScript?
- Any plans for SDKs or libraries? Example code in popular languages perhaps...
- How is this different from Parse? (Except less developed)
Also, some feedback:
- Make it easier to understand the main benefits quickly, I had to read the small text
- I love the simplicity of the product, keep it simple - The pricing is weird... Not sure what to recommend, but $1.50 just seems weird. Too low?
edit: formatting
http://martinfowler.com/bliki/FeatureBranch.html
After reading this article, I now realise why having only one branch is desirable for a small team using CI. The development style should use things like feature toggles to ensure that code paths are not activated.
Branching, as I've thought of it, relies on the SCM to segregate features instead of developing robust and modular features that can be swapped in/out willy nilly.
The team I work on is quite small, so I can see how not using branches can work. I've worked on larger teams and I can't imagine how we would have managed those changes without an excellent branching model (git-flow).
Seems to me, in the case of a world where bandwidth is scarce and processing power is ubiquitous, that the fat-client, thin-pipe model is where it's at. :)
How many cycles have you seen? Are they really comparable? Doesn't each one need to be treated specially and considered independently?
I was once obsessed with productivity, and for me it came down to an attitude of 'just do it'. This was filtered out into various micro-level attitudes and behaviours, many of which are discussed in this article... However, I now realize that going back to University sapped me of all this yet again: I was in the world where smart guys reign supreme. This is the reason why the smart guy pitfalls exist at all: there are artificial worlds where we can somehow glide by just by being smart.
The real world is real, and it takes real work to stay on top of your shit.
Some things I used to do that I will start doing much more again:
- Write everything down
- Make todo lists
- Try to actually measure productivity (http://www.rescuetime.com)
- Be realistic and conservative with estimates of how long things can take.
--Not really knowing how long something will take should be scary.
--Do a quantifiable percent of a task, time it, extrapolate.
- Stop borrowing time (and money).> access main security system please
> display zebraGirl.jpg