tech things. . It's look much about the application domain and business logic. A few days back I viewed a senior continously interacting with his boss(owner) on a web ecommerce site. Like how things should be done. Dialoguesike "Whether this accounts id of that employee should be saved before or after kind of" dislogues... it's seems knowing the business domain , understanding the whole internals logic of the application is imminent. Here c# knowledge play a minor when compared to, I feel. Seniors here pls provide your opinions.
How self taught, who do their own projects gather that level of knowledge on application logic and various requirement on his/her practice doings?
tbh I don't like more this continously interactions with others. Fir eg if one is doing cms project or erp, then it seems beforehand one must have the knowledge of "a how a crm application or erp applications fit various pieces together and how the logic is designed", is vastly paramount to have. Here .net knowledge takes 2nd seat.
I am more interested in c# side than this application domain and specific business logic. I think cs beauty is entirely different though. Systems programming, network programming are I guess that does not involve external knowledge of application domain nd business logic.
so we are not tech persons , it's suit to address we are a "cms person who use c# or we are a erp person who use c#"
You're working for somebody else. Priority number one is what that person wants implemented and how
Yea we gotta implement solutions for others ideas. It's not something purely technical. Do you love that ?
Nobody loves that, it's just a trait of being a programmer working for other people. If you don't want that part then you should make your own company so you can make your own choices. Corporate interest is never going to change
Обсуждают сегодня