I like to get my hands dirty, and I often give live demos to other departments about technologies they should consider. Most architects live on whitepapers and theory. Browsing the right forums (like this one, albeit this subreddit is 90% career related these days) helps.Īlso, testing testing testing. It's something I enjoy and do in my spare time, which is probably how I got the job to begin with. An architect is usually in the right position to be able to make those changes without letting reputation/ego get in the way.Īside from that, research research research. Being able to accept feedback and adjust the plan based on that feedback is important and part of an architect's job as well.Projects will get mired in indecision very easily. Especially in larger companies, it's just about making a decision and being there to push back against wafflers.If your senior executives have a hard-on for a specific technology, you aren't going to win any friends by dying on a hill for a competitor. You need situational awareness about your office politics.Sometimes doing something just because that's the way the company has always done it is acutally the right decision - especially when shifting only has a marginal benefit.That said, there are plenty of wrong choices. There is never a "correct" technology.In reality its about understanding several truths about technology. If you want the bureaucratic answer, it's about choosing solutions that rely on established technological patterns and minimize tech debt and bleearargh I threw up in my mouth a bit. It might be OK to talk about the merits of an interview process, or compare what has been successful at your company, but if it ends up just turning into complaints your post might still be removed. There is no interesting/new content coming out. This has been re-hashed over and over again. No questions like “Should I learn C#” or “Should I switch jobs into a language I don’t know?”ĭiscussion about industry direction or upcoming technologies is fine, just frame your question as part of a larger discussion (“What have you had more success with, RDBMS or NoSQL?”) and you’ll be fine.Ħ. This includes almost any discussion about a “hot market”, comparing compensation between companies, etc. General rule of thumb: If the advice you are giving (or seeking) could apply to a “Senior Chemical Engineer”, it’s not appropriate for this sub.Īsking if you should ask for a raise, switch companies (“should I work for company A or company B”), “should I take offer A or offer B”, or related questions, is not appropriate for this sub. Career advice threads may be removed at the moderators discretion based on response to the thread." This sub is for discussing issues specific to experienced developers.Īny career advice thread must contain questions and/or discussions that notably benefit from the participation of experienced developers. Violations = Warning, 7-Day Ban, Permanent Ban. This includes posts that could be interpreted as trolling, such as complaining about DEI (Diversity) initiatives or people of a specific sex or background at your company.ĭo not submit posts or comments that break, or promote breaking the Reddit Terms and Conditions or Content Policy or any other Reddit policy. No racism, unnecessarily foul language, ad hominem charges, sexism - none of these are tolerated here. If you have less than 3 years of experience as a developer, do not make a post, nor participate in comments threads except for the weekly “Ask Experienced Devs” auto-thread. Do not participate unless experienced (3+ years) This community leans towards being a specialized subreddit facilitating discussion amongst individuals who have gained some ground in the IT world.įor an idea of what is encouraged in this subreddit and what is not (please report anything that does not follow the rules): Rulesġ. Welcome to the /r/ExperiencedDevs subreddit! We hope you will find this as a valuable resource in your journeys down the fruitful CS/IT career paths.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |