1,538 karma · joined November 28, 2013
Email is AVI at AVI dot IO
The value proposition here is incredible, you can save so much money for companies.
At my previous company, I changed one of the data ingestion architecture and saved 250,000$ in YEARLY AWS bill.
Of course, there are many problems with this, but I still think there is room for this. Right now, this knowledge is in silos in companies. Lots of companies should benefit from this.
This!!!
Coming from the travel business. I remember this vividly.
You acquire a customer that is not loyal to your product even for 3 seconds for 1$ and you make 0.8$ out of that customer.
Building a customer acquisition strategy that will work in the long run and will make you money is such a key realization.
Even if it takes you longer and seems like you are moving slower, you should not be tempted.
At one point, we saw a 200% increase in users over the course of two weeks due to some "growth hacks". Those ended up just costing money in server and engineering costs. None of the customers actually stuck with the product for the long run.
All of our services use credstash to store secrets. We use KMS in order to encrypt, decrypt the secrets and when the app loads we load all the secrets into memory.
There was a major change to cryptography that caused credstash to break and in turn break a large set of our services.
This PR [1] was submitted by one of the engineers to force the lower version to credstash and we opened the dependencies again to reload credstash on all services.
The process to track it down and fix it took about an hour and all services were building correctly again.
We make a very conscious choice to break those things in real time and deal with them rather than hiding them behind locked dependencies you simply never upgrade.
The attention to detail and care he put into this product was really inspiring. Seeing this rise from the ground into a finished product was great.
Personally, I love that this does one thing really well and integrates into your Trello board (if you want). It really helps with collecting feedback from your customers.
[1]: twitch.tv/omatum_greg
I am very impressed with Square constantly. It's really amazing to see what they accomplished.
For us, we have a review process internally for every 3rd party we use. We figure out the auth process and how secure is it etc...
As much as I hated it at first, we don't choose any provider that doesn't support single sign on and multiple users.
You can choose a password policy that is different (stricter) than the downstream services.
One more good thing about it is that you have all of your services in one place and you know when you need to change password on one of them or all of them. You can do it with a nice dashboard.
This made managing access a much nicer experience for us and I can imagine will minimize things like that from happening.
Let's say you make 100K today if someone offers you 120K that's a 20% increase. BUT, what happens if you get fired or quit after 2 months. How long will it take you to find another job and how likely are you to match that 120K or 100K?
If the answer to that question is not "a week", the job move should make sure this risk is smoothed out. Usually but a signing bonus on top of the pay increase or something like that.
Not saying that every job should have a signing bonus or that you should hard require it, just saying that pay increase is not the only thing to look for.
1. What do you want me to do when I hit that page? Just randomly browse around until I find something?
2. It is very unclear what the product is for and why do you expect it to stick. I think for a product like this to stick you will have a very hard time explaining the benefits.
3. Considering this is for "completionists", every list I see is basically empty. Not a great motivator.
There was a similar startup a little while ago: https://angel.co/complete
[1] https://www.facebook.com/RobertScoble/posts/1015578291863465...
The pain is definitely real. We had a 6-year-old rails app that got upgraded from Rails 2.3 and keeping track of dependency decay was painful.
Looking at your landing page, I could not understand how are you solving the problem exactly. The screenshots don't expand so I don't really get the solution.
One very nice feature that you can add and will help a lot is to support comment parsing in the Gemfile and Gemfile.lock. Something like email: my@my.com. When you parse the file, send me the report and don't make me actively visit the page.
Also offer a sample report on your page by submitting a public repo perhaps.
Good luck!
The only thing that 3rd party JS will have access to is everything on the page.
Now, the things on the page are sensitive (the secrets from the env variables are dumped in the UI).
Secrets in the secrets page are not exposed at any time, even when you go to edit. Only in the build screen, it's exposed to the output.
Those 3rd party libs DO NOT have access to your source code at any time. The only time they will have access to your code is if they gain SSH access to the machines that are running the build. And that's not trivial.
Even if your public key is exposed, they don't have access to checkout github with that.
So yeah, it's 3rd party libs in a "private" context but not more than that IMHO.
I have been running mock interviews on Twitch for the last couple of months now, and the responses are incredible.
You can check out previous interviews on the YouTube[1] channel.
You can also hop by the Twitch[2] channel. I usually stream three times a week at 8 pm PST.
The interviews are 100% free and offered as a community resource. You can maintain anonymity as well. Feel free to jump on the discord [3] if you want to schedule one
[1] https://www.youtube.com/channel/UCuFT6CtDnOGvcn9WdAvBusA
It can also stream the video back to my computer so people on the stream can see where the car is going.
https://fullstack.network/i-built-a-car-that-is-being-contro...
This is really common practice and I hated every bit of it.
Everyone is looking at the big guys like Expedia and Booking.com and those are really pushy. You can see them popping up every thing in a popup.
You're looking at a room and you see "1500 people are looking @ this room now", everything, just to get you to book.
This case is a bit extreme, even in those standards, but not the first time I see something like it.
1. Coverage. Where are you located and what's your service area. (I did see it at the bottom in a small font, it's not enough) 2. Price and general conditions. Should be the front of your service. Just like the uhaul trucks. IMHO. 3. More pictures of the car/cars. Could it fit my family? Could it fit more equipment than what you initially put in it?
There's just not enough details on the landing page to get me interested enough to even drop an email.
I really like this! Lots of people I talk to think: I will put this on the internet and people will find me. Hustling to get to your crowd is a great way to make sure you get consistent traffic. Kudos on this
Google made quite a bit of changes to the algorithm and hurt almost every travel product in favor of it's own products.
I wonder if you were effected by this at all and what did you do to deal with it?
The point on the speed for me wasn't that speed as a whole doesn't matter. Speed in the language level doesn't matter.
If you do stupid shit with rails it will take 5.1 seconds and if you do stupid shit with Golang it will take 5.05 seconds. It simply doesn't matter all that much in the language/framework level for most of us.
For example: In my current job place we are using Flask for all microservices. One of the endpoints was very slow to respond and took 3 seconds. It ended up being a missing index in the DB.
Once fixed it's taking 20ms.
So, Is python slow because it's taking 20ms vs 12ms?
Most of the companies I talk to today, don't choose Ruby. They mostly go with JS (Either express or Meteor or others).
The "Hate" for me is articles like this. Don't know if "Hate " is the right word.
All of our microservices are written in python and gateway to services are written in Node.JS.
I am not comparing Express to Rails feature to feature (which if you read my other comments you understand I am against).
Anyway, welcome to HN!
It is great that as your first comment you say someone else's comment is silly.
I am not going to try and answer these, it will be idiotic but all of these articles and some of the thrust behind leaving Ruby and these articles are just driven by the wrong reasons.
This is a classic case of weighing solutions against other solutions. When you do that the one with the most features or the fastest will always seem the best.
But, you need to weigh the solutions against your problem.
Your problem is time-to-market. Your problem is development time. Your problem is software reliability. Your problem is finding great engineers to do great work.
When that's your problem. Ruby and Rails are great solutions. Not good. Great solutions.
Show me an express app that is as monolithic as some Rails apps and I will show you how Node.js halts to a crawl.
[1] https://twitch.tv/kensodev
EDIT: Typo
One thing I would like to say is that the development experience with Ruby/Rails is by far the best out of all of these languages. By FAR.
The way you can start a project in a second is amazing, the TDD experience and Rspec integration with Rails is simply mind blowing comparing to anything else.
Express might be 100% faster than Rails but it will take you 5 days just to get something running vs what you can do with Rails in a matter of minutes. From Authentication to Authorization and all the community around these.
Regarding the fast/slow it's simply bull-crarp, seriously. It DOES NOT matter for 99% of us. It simply doesn't.
Most of the slowness you are experiencing in Rails and Ruby apps is by doing poor engineering, not by Rails or Ruby itself. Big Surprise... If you query 1000 rows and bind them to the controller things will be slow.
There are things that are natively slower, JSON parsing and marshaling for example is one. It's much slower than Go for example but it's so much easier and for 99% of us, this is what matters.
I don't get the hate that Ruby and Rails are getting. Really don't.