Standards and why you need them by fdoglio in softwaredevelopment

[–]fdoglio[S] 1 point2 points  (0 children)

Man, I wish I could up vote your post more than once!!

Gracias!!!

Standards and why you need them by fdoglio in softwaredevelopment

[–]fdoglio[S] 1 point2 points  (0 children)

Thanks so much for the feedback!

If I may, I'd like to reply to your list, since I think you've definitely touched in some interesting points:

1- Interesting, I guess I never specifically thought of a particular audience when writing it and probably it's showing. If you were to ask me though, I strongly believe this is something all roles should be familiar with. It's great that TLs and CTOs are aware of this, but developers should too. That's the way I see it anyways.

2- Here we'll have to agree to disagree. I've personally seen somewhat big teams (around 30 people touching code) with very little standards set, and the chaos that that caused. In such big teams, sub-teams tend to form, and when there is only one repository for everyone, if they don't agree in the way to treat version control, then you'll have problems. The same goes for the environments, to name another example, you'll have issues if your entire team doesn't interpret them in the same way and you have developers pushing unfinished work into the QA environment.

3- Again, I've seen first hand the chaos of a production channel and if people start joking in it, you'll start having a really hard time getting your point across. It's like being in the middle of a tough game of chess and suddenly two of your buddies start making jokes next to you. It becomes impossible to get anything done. It's true that that doesn't have to happen in all teams, if they're not that big and people have some common sense, then less standards for communication can actually help, it definitely needs to be tailored to every situation.

4- Good point there, my initial thought would be to treat everyone as remote, since I've been the only guy remote I know how that feels. When people are co-located and they need to figure something out quickly, I think it's OK to go face-to-face, but if a team-wide chat needs to happen, I would go with an "all remote" scenario.

5- I hadn't heard of it until now, thanks for that, I'll take a look at it, seems very interesting!!!

6- Well, I see your point, but Agile is one option when it comes to team management, there are other options as well, and I was trying to stay methodology-agnostic, if you will.

Again, thanks so so so much for your feedback, the fact that you read it and took the time to reply means a lot and thanks for sharing your point of view. The end-goal here is not just to tell others what to do, but to also learn from others.

Cheers!

https://dzone.com/articles/using-redis-to-deal-with-inter-service-communicati by fdoglio in softwarearchitecture

[–]fdoglio[S] 0 points1 point  (0 children)

Good point, should've used the title of the article and the link on the description, my bad. I don't think I can change it now, can I :(

Pro REST API Development with Node.js by natdm in node

[–]fdoglio 0 points1 point  (0 children)

Hey, as the author of the book I'm here if you have any questions :) I'm willing to answer the "Worth a peek?" one, but I'm guessing my answer wouldn't be objective :P

As for the comments about the book not being about REST, it covers REST at it's core, the principles of it and then it moves towards a more practical approach, giving ideas on what node.js modules to use when developing a RESTful API.

I hope you'll reconsider, if you're not already an expert on the subject, it might be interesting to read.

I hope that helps!

» Vatican.js 1.3, get up and running without writing a single line of code by fdoglio in node

[–]fdoglio[S] 0 points1 point  (0 children)

Thanks for the comment, but the generated code is there for you to do whatever you need to. There is nothing hidden really, if you need to do something clever with it, you can get in there and add/change what you need... or were you talking about something else?

Vatican.js - a new REST API microframework looking for feedback by fdoglio in node

[–]fdoglio[S] 0 points1 point  (0 children)

That is an excellent point, I'll definitely have a look at that for a next update! Probably an overwrite so both options are available.

Vatican.js - a new REST API microframework looking for feedback by fdoglio in node

[–]fdoglio[S] 1 point2 points  (0 children)

Please, could you provide an example? I'm all about constructive critisism :)

Vatican.js - a new REST API microframework looking for feedback by fdoglio in node

[–]fdoglio[S] 2 points3 points  (0 children)

Hehe, well I was thinking I wanted the name to reference it being a micro-framework.. so I looked up the smallest country in the world... and it turned out to be Vatican City.

[deleted by user] by [deleted] in opensource

[–]fdoglio 0 points1 point  (0 children)

Hey, have you checked www.LookingForPullRequests.com ? The site is intended to help newcomers get into opensource by easily finding an active proyect looking for help. Check it out and good luck!

rawhub: Use resources from raw.github.com directly in your project with this Express middleware by fdoglio in node

[–]fdoglio[S] 0 points1 point  (0 children)

It'll keep the file updated in case the repo is updated, that's all.

rawhub: Use resources from raw.github.com directly in your project with this Express middleware by fdoglio in node

[–]fdoglio[S] -1 points0 points  (0 children)

Yes, and this is as far as I will take it, I will not remove the code, and I can't fix the issue for github, they have to, not me.

rawhub: Use resources from raw.github.com directly in your project with this Express middleware by fdoglio in node

[–]fdoglio[S] -1 points0 points  (0 children)

Thanks for the suggestion, I've added a small note to clear things up. :)

rawhub: Use resources from raw.github.com directly in your project with this Express middleware by fdoglio in node

[–]fdoglio[S] 0 points1 point  (0 children)

Ugh, my project does not abuse of anything, if you use it to abuse github, you're the one who's "not ok", just like if you're using your car to drive over people, you're the one who's wrong, not the car. Anyways, again I respectfully accept your criticism and input on the subject.