borracciaBlu

I was writing a small article about [Set, Set Builder Notation, and Set Comprehension](https://adropincalm.com/blog/set-set-builder-natatio-set-com...) and while i was investigating it surprised me how many different ways are to describe the same thing. Eg: see all the notation of a Set or a Tuple.

One last rant point is that you don't have "the manual" of math in the very same way you would go on your programming language man page and so there is no single source of truth.

Everybody assumes...

The article conclude stating that you should still know more than maps and decide by your own, but it gets against the whole idea of using the apps in the first place.

I do use google maps because it has more information than i do else i wouldn't use it at all.

In particular, i think the story is the perfect case of what's happening when the only metric available to evaluate a route is ETA.

I would say this is a missing feature which i would call `Route difficulty` or similar.

This would be the same concept used in some cooking recipies that have tags stating if the recipie is doable for a beginner.

I think, as part of the `Route difficulty` metrics they could use:

- number of petrol stations and distances

- road slope (more than 30 deg could be challenging)

- traffic (if something happen, how many people will pass by to have support)

Having this additional metrics would make the life so much easier and safer to evaluate the best route to take.

If think about estimate as learning activity in the sense of Theory Building, then you won't really care about the estimate by itself (which is a nice by-product) but as a confirm that the task is clear and actionable. In that the real value I think.

I've been witness of developers not working in isolation, with clear specs and requirements, who knew what was the expectation and still use the tech they preferred.

I would say they were unprofessional and selfish. Not great as cultural fit neither.

Discipline should came first. Imagine you go to a restaurant and order a pizza and instead you receive sushi just because the chef wanted to learn a new cooking style..

Hi nik3r do you have any screencast using the product? If so, could you share the links pls?

do you still fill productive with your phone on the desk?

Sorry, forgot to mention sublime!

I do. I work with Linux and on my company we use exchange..

A part for that I pay for: - Skype credit - gitkraken (thanks electron!)

And i would pay and pay and pay for a design software like sketch.. I have a lot of hope on figma.. Let see..

Another point that probably it's worth explaining a little bit more is the concept of exploration. aws-upload has been designed with the idea of brain zero.

Which it means: I'm lazy, I don't want to remember all the projects or environments I got.

When I was using the aliases without the scope I had to remember each label for at least each project.

With the trick of the scope I could tab, but with 10 projs with 3 envs each, you start to have 30 suggestions.

Too much noise for my taste.

With aws-upload the only thing to remember it's aws-upload itself. Then I tab.

I hope it clarifies a little bit more.

Sorry you right, the "Why?" section it could be better about the difference with an alias.

So, if you are working alone an alias is perfectly fine. If you are disciplined you could use a convention like `upload_blog_dev`, `upload_blog_stag`, `upload_blog_prod` and everything should be more or less fine.

I say more or less fine because if you are editing an alias 3 lines long you may have some typos or configuration issue (I'll talk later about that) and it can be far away from to immediate to detect the bug, edit the aliases file or the (.bashrc|.zshrc) file and reload the shell.

With aws-upload and tmux, I edit the settings in one panel and test in the other. Real time, no reload.

Which kind of issue can you face with this kind of task?

From my experience, I would say at least 3.

- the folder you are trying to upload doesn't exist (wrong path),

- the pem file you specify doesn't exist (wrong path)

- the pem file exists but it has wrong permissions.

Alias doesn't give you any support to debug these issues, aws-upload has the cmd `check` to do that.

The thing can start to be more tricky if you have a colleague that need the alias for him/her and potentially has exactly to edit these values in the alias.

In this case what you have to do is open the alias file, find the row with the alias you want and send it. In aws-upload you have the setting file in ~/.aws-upload . You send it.

Think that, if you to have a lot of aliases the alias file can start to grow exponentially, and of course, the possibility of mistakes and losing time grows as well.

Instead aws-upload reduce for you the scope of the critical information you have to manage and it tries to support you during the process.

Useful cmd in these situations:

- aws-upload check key // it check folder, pem file and permission

- aws-upload new key // create new setting files

- aws-upload cp oldKey newKey // copy a setting file

- aws-upload edit key // edit setting files

I hope it makes a little bit more sense now.

Do you have any interesting case about the use of "delicious"? I would love to see them, I'm a case collector.

Thanks

> Delicious rationale:

What I was trying to deliver was the idea of fresh, new, elegant, alternative, easy to use, geek, beautifully designed, young, for future generations.

I tried several combinations before the current tag line but no one of them seems good to me.

+ Some alternatives:

-- aws-upload a great CLI Tool for uploading files to ec2 // simple

-- aws-upload an elegant CLI Tool for uploading files to ec2 // may be, but old

-- aws-upload an alternative CLI Tool for uploading files to ec2 // wired

> Rainbow rationale:

The idea I was trying to deliver was that aws-upload can be "a kind of bridge" between you code on localhost and your servers. And the rainbow looks like a kind of bridge, a magic one if you want.

If you have any idea or suggestion let me know.

As I said work on it. You can differentiate by customers type (b2b or b2c), business model (subscription, advertise, once time payment, remarketing), features (mobile, web, offline) just to say some.

I think that have few competitors shouldn't worry you till the moment that delta between your product and your competitors it's solid. I would be even relieved about such a thing. You are not alone betting on this type of market.

Just to clarify the delta point. How can you be sure that the difference between your product and the competitors one is reasonable?

Try to use the product vision statement from Geoffrey Moore’s book Crossing the Chasm. http://elevatorpitchessentials.com/essays/CrossingTheChasmEl... Try to see if your point [5 (Unlike)] is solid enough compared to your competitors. If not, work on it.

I would think twice before to throw everything.

I got a new landing page + docs. If you have any feedback/opinion is super welcome. Especially about the docs.

Thanks

I'm working on an open source project that may be it could be interesting for someone.

The project is a cli tool to upload files through rsync. The main point is the api. You define a json file for each project you are working on and then you are able to upload from cli.