3 ms·
> The main point I wanted to make is what jeff-davis (your sibling) summarized for me with words way better than my own: "If you are building something and exci
by pdimitar 6y ago
> The main point I wanted to make is what jeff-davis (your sibling) summarized for me with words way better than my own: "If you are building something and excited, then keep going, don't stop because a blog told you 'never'"
This is a weird perspective. Most of us work for money and other people are calling the shots on what's in priority to develop right now. Your statement reads like you're commenting about hobby projects?
> Too often I read blog posts like the one we are commenting when I was starting with software development as a job, they scared the shit out of me!
Not to be reductionist, just trying to understand: your point of view boils down to "I skipped a good tool because I bought a fear-mongering tech blog article", is that correct?
If so, obviously one has to form their own opinions as they gain experience. But I wouldn't feel that strongly about those articles. My takeaways are: (a) critical thinking is important and (b) you can't ban people from posting. ¯\_(ツ)_/¯
> I didn't have any experience on the tools so reading that some much more experienced guy working on some Silicon Valley billion dollar corporation was saying "This is shit: you touch it, you die" didn't bring anything useful to me, just stress...
Not sure what point you're making here. Our job is riddled with stress in general (even if you only take this as an entry point: the brain hates learning and wants us to stay still by default). Confronting that reality means exiting software development for many.
> your personal experience, be it success or failure, is worth a thousand times more than the success or failure narrated on a random guy/girl blog from N years ago
That is absolutely true. But we should recognize filter bubbles regardless. I for example only heard one successful MongoDB story and the team switched to another DB 3 years later.
---
If your general takeaway is: "use whatever you want" then sure, nobody can dispute that since we live in a free world. However:
(a) When comparing tools for certain jobs, there are objectively worse tools compared to others. This reality should not be avoided, or denied, or brushed aside with generic statements.
(b) "Just use whatever you like" is not a sound career advice. Some tools will give you better career opportunities, others will make people frown at you for being the bleeding edge adopter but can give you a competitive advantage, and some will just burn you.
It's not about if you can achieve X with any technology. For the most part, you can do pretty much anything with everything. Still doesn't make it viable or the solution with the least friction and most reward though.
I felt your comments were too generic, too optimistic, and rather uninformative. Hence my responses.
- 01acheru 6y agoI could go point by point on the first part of your reply, but there is something underlying your view that makes me feel we come from places that work a little different. I don't know where you're from, I'm from Italy so let me put down some points: - here almost every single company is incredibly small (average is 4 employees) - we have lots of companies (66 every 1000 adult citizen) - IT panorama here is like 15 years behind the US - after university or technical school you know almost nothing, just some basic abstract notions So you have to learn every single thing by yourself, and if you want to work with today technology you will not learn it at $WORKPLACE because your boss probably is a 60 years old guy who wrote COBOL programs but want you to build "something like Facebook in the next two weeks". The only window we have on today technology is on the internet, many tools that come cheap somewhere else are quite expensive for us and you must be lucky to know that one guy that can give you some hints. In my case I've studied in technical school and then did IT engineering at the local university, which I dropped with a couple of exams to go after I had to argue with a professor that solved it's own exercise in a broken way and couldn't understand why my solution worked. In the last 15 years working, until now, I didn't know anyone here in my hometown who can work with anything outside some legacy ASP stuff, basic PHP on CMSs like Wordpress or some basic Java applications (mostly Android), DBs are always MySQL. Just a friend of mine who uses QT, which he learnt by himself and after changing three jobs now he is finally in a dev team, but on the previous three he was the only dev in the company. (I know other people that work with "today's" tech but they are not from my province) I don't know if I can communicate my point, but reading that $PERSON who works at $COMPANY says that $PRODUCT is shit because he had problems scaling to 100mln users is a totally useless point for all the people outside the few tech bubbles around the world. It's not about "everything is good", I never said that everything is good, but in the real world™ people built great things using almost any tech, maybe even "uncool" tech: it worked, they made money, they were successful, their company served customers for years and years, and maybe the chosen tech had a positive role in the process. My point is about people that say "Never", "Always", "This is broken", "You'll get burned", "It doesn't work"... that's the part that is not constructive: it didn't work for you, for your case, maybe you did some mistakes, but $PERSON must stick to his/her own reality, not try to extend their experience to everyone else.
- 6y ago