Knowledge sharing at the job?
-
Really? Pro-devs. who did that? :rolleyes: :-D I suddenly feel a (tiny) bit better... I work in Local Government (UK) :zzz: and I've sort of 'inherited' all things IT - DB stuff, software development (when it suits the higher food chain), reporting, what laughingly passes for analysis/stats, etc. Training is Verboten!!! (never mind encouraged) and pay is still crap. One thing I have noticed over the (interminable) years - if 'they' are desperate (like, 'we need this yesterday to make me look good') then I'm allowed to play - else it's 'software suppliers only' (for the 'support') ;P Bitter? Probably. Frustrated? You bet. Just too near retirement to move..... :sigh:
Ha yes, I feel your pain...... Contractor here who's worked on both government, NHS and UK Military projects in the past. :-) It's soul destroying at times.
-
There you have it: in your "free" time means on your "own" time. Nobody likes studying "for work"; on their own time. There was a time when one was sent "out of town" for a course (which included meals, hotels; maybe a car).
"(I) am amazed to see myself here rather than there ... now rather than then". ― Blaise Pascal
I happen to like programming so, yeah, I study quite a lot in my free time. My employer profits and then I profit (being the best they have tends to give leverage) :D
Best, Sander Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
-
I happen to like programming so, yeah, I study quite a lot in my free time. My employer profits and then I profit (being the best they have tends to give leverage) :D
Best, Sander Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
Being the "best" isn't always what it's cracked out to be. The "budget" needs to be split amongst everybody; meaning, "if I give you x then they ONLY get y and then they are unhappy, etc.". It then becomes tests of wills. (If you happen to actually like what you are currently working on, then that's a different story; but that will get "old" too after a while if you like to stretch; or see new faces).
"(I) am amazed to see myself here rather than there ... now rather than then". ― Blaise Pascal
-
Sander Rossel wrote:
Was your education in your boss's time?
When I worked for Goldman Sachs, it was on my employer's time. I have had it both ways for education, etc. I am a contractor now, and I work from my home office. They expect me to learn everything on my own. Which is fine, and I do, but I miss the collaboration and knowledge sharing.
-
Wanna learn something quick? Get asked to deliver a project with technologies you've never used before, within a fixed amount of time (that you'd barely think reasonable if it was done with what you do know).
True story: - I think we should go .NET. - No; Java. - Me: Struts; Swing; Beans; Eclipse; JBoss; Linux; Apache; etc; Java-related courses out of town... - (weeks later) OK ... you can use .NET.
"(I) am amazed to see myself here rather than there ... now rather than then". ― Blaise Pascal
-
We're not talking about best practices, we're talking about not knowing the basics after years of usage and a really buggy application as a result :sigh: Entity Framework lesson 1: ToList() does a query to the database and gets the results. Application after years of work:
context.MyTable.ToList().Where(o => o.FullName == "...") // Because somehow FullName does not work on the database.
// In MyTable entity:
public string FullName
{
get { return FirstName + " " + LastName; }
}:sigh:
Best, Sander Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
Has to do with "ownership". I'll "own" my projects; so there are no issues. But once someone else "takes control", I can no longer be responsible. If that other party won't "own", then the "technical debt" accumulates.
"(I) am amazed to see myself here rather than there ... now rather than then". ― Blaise Pascal
-
Has to do with "ownership". I'll "own" my projects; so there are no issues. But once someone else "takes control", I can no longer be responsible. If that other party won't "own", then the "technical debt" accumulates.
"(I) am amazed to see myself here rather than there ... now rather than then". ― Blaise Pascal
I don't see what ownership has to do with understanding your tools :confused: This was code written by the team that worked on it from the start and they were still writing it like that. Ownership or not, you won't write code like that if you know what you're doing.
Best, Sander Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
-
Being the "best" isn't always what it's cracked out to be. The "budget" needs to be split amongst everybody; meaning, "if I give you x then they ONLY get y and then they are unhappy, etc.". It then becomes tests of wills. (If you happen to actually like what you are currently working on, then that's a different story; but that will get "old" too after a while if you like to stretch; or see new faces).
"(I) am amazed to see myself here rather than there ... now rather than then". ― Blaise Pascal
Never had any trouble with budgets. More that I'm willing to try new stuff and better the application while coworkers are afraid of innovation and get stressed out and/or angry. I've had a coworker scolding at me because he literally couldn't read some C# syntax I had used (I used some delegates, nothing fancy). Ok, that guy was really bad at programming and at social skills, a terrible combination :sigh:
Best, Sander Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
