3 ms·

Here's my subjective part. After 5 years, it was fun. 2006. And things were blooming everywhere. I barely knew what things _not_ to read or try. After 10 year

Here's my subjective part. After 5 years, it was fun. 2006. And things were blooming everywhere. I barely knew what things _not_ to read or try. After 10 years, I began to grasp that tech itself, its mastery, is the worst predictor for a project/company/thing's success/adoption. It's important, but the essence of "it sells" is somewhere else than in "it works, it makes sense and it's beautiful". After 15 years. I'm full of doubts. I skimmed enough in the IT world to see different communities/companies that work/think so differently and apart that "the IT world" is fragmented (broken?) to the extent that someone who's a productive expert in their field in some group, will not understand, and not be capable of working in some other group. Although they use the same technology, speak the same language, could work in the same country, for the same customers, but they organize and plan differently, think differently and optimize for different outcomes. Now for the tech part: it's like when you begin to be more fluent in languages: the more you learn, practice, experiment, play, discuss about, the more you grasp the history, the wider your wold view grows, of how things were, how they are, where they could/should go. Tech as language is a tool. It's the people you do things with that matter in the end. As, you'll realize, it is as in any other field (from pastries to warfare).

daryllxd 9y ago
Thank you for answering. At first I was surprised at "someone who's a productive expert in their field in some group, will not understand, and not be capable of working in some other group", but I guess at some level I as a Ruby/JS (and learning Elixir) programmer am drifting apart from the other languages. Like right now I can't visualize myself coding iOS/Android apps just because the tooling is different. I probably could if I really wanted to, but it'd be really hard. My goal for the next few years is to just keep on mastering the craft as to make it easier to make things or make decisions on things, I hope to continue programming to at least make tools for myself and for other people. I completely agre re: "its the people you do things with that matter", but I'd like to add "the people you do things for", too. I think everyone (bakers and soldiers included) likes working with nice people and working on something that will be used by other people.
- twunde 9y ago
  I think the parent was talking less about the differences between programming languages and more about the differences between a programmer working at an early stage startup and a programmer working at a large enterprise company. They are going to go about doing their work in two very different ways. The way they speak, their concerns and the best practices for programming will differ.

daryllxd 9y ago

Thank you for answering. At first I was surprised at "someone who's a productive expert in their field in some group, will not understand, and not be capable of working in some other group", but I guess at some level I as a Ruby/JS (and learning Elixir) programmer am drifting apart from the other languages. Like right now I can't visualize myself coding iOS/Android apps just because the tooling is different. I probably could if I really wanted to, but it'd be really hard. My goal for the next few years is to just keep on mastering the craft as to make it easier to make things or make decisions on things, I hope to continue programming to at least make tools for myself and for other people. I completely agre re: "its the people you do things with that matter", but I'd like to add "the people you do things for", too. I think everyone (bakers and soldiers included) likes working with nice people and working on something that will be used by other people.

twunde 9y ago
I think the parent was talking less about the differences between programming languages and more about the differences between a programmer working at an early stage startup and a programmer working at a large enterprise company. They are going to go about doing their work in two very different ways. The way they speak, their concerns and the best practices for programming will differ.