When to stop learning...?

[prabha_friend]

You know... Requirment is just a purchase request form but my mind says: "Why not a notification for each request?". Okay somehow notification also done. Again my mind: "Approve, Abort features" would be nicer...

 

[The_Doc_Man]

I will answer the title question.

You stop learning when you are dead. At which point you can only hope that others have learned from your examples.

 

[jdraw]

You know... Requirment is just a purchase request form but my mind says: "Why not a notification for each request?". Okay somehow notification also done. Again my mind: "Approve, Abort features" would be nicer...

This is how SCOPE CREEP kills many projects.

 

[Cotswold]

Am I still learning, or am I just forgetting the stuff I have already learnt? So having to do it all again.

 

[NauticalGent]

This is how SCOPE CREEP kills many projects.

Or keeps me employed - at the cost of my religion, sanity and hair...

 

[jdraw]

Yes -- a key to a long career in IT.
Aside, John, I thought I saw you recently.

 

[NauticalGent]

Indeed. We have been a a few rides recently. We have come to the conclusion that we don't like the large crowds so we are going to do our own thing. Might start our own MC - call it the "Sore Thumbs MC"

 

[NauticalGent]

Reading the OP's question, I wonder if he meant to ask "At what time do you say 'no more changes' to the app you are developing?" The answer is the same: Never - except if it is on contract, in that case the answer would be when they stop paying you.

 

[jdraw]

Brings the meaning of Per Diem vs Fixed Price to the fore. On a Per Diem-- ask for anything, we can do!
If it's fixed price --read the fine print. Nothing, not in the contract, is included. Any and all changes are separately billable.

 

[The_Doc_Man]

I guarantee you, there is NOTHING that makes a sales person grin like a customer who comes back and says, we need to initiate a change order to our original specification. We used to bid our initial control systems so that they were indeed functional as specified, but it never failed that the customer suddenly remember that remote data collection unit somewhere east of nowhere that just HAD to be included in the scope of work. Oh, we were pretty fair about it. But unlike the initial contract where everyone sharpened their pencils, with change orders we could use crayons and didn't need to color inside the lines to make it pretty.

 

[MsAccessNL]

I will answer the title question.

You stop learning when you are dead. At which point you can only hope that others have learned from your examples.

I think that learning is a very essential part of life itself. Life is one big learning experience. If you are religious or not, somebody or some entity or life itself, istrying to teach you something, if you can’t crasp that, you will miss the true essence of being alive..

 

[Cotswold]

You stop learning when you are dead.

This being the case then may we all at access-programmers never stop learning.

 

[GregDataReno]

It's a phenomena - I can't tell someone what I know until I'm asked, or if I have to solve a problem. Over time, an ability to solve a problem becomes - well - unsurprising; I assume that's 'master' level?

 

[The_Doc_Man]

It's a phenomena - I can't tell someone what I know until I'm asked, or if I have to solve a problem. Over time, an ability to solve a problem becomes - well - unsurprising; I assume that's 'master' level?

Knowledge is not always a concrete thing, really. It can be very abstract and seem to be fleeting. You don't know what you know until someone triggers your memory related to that knowledge. For you to try to self-evaluate what you know is difficult. "Master" level can be a euphemism form having experience. But experience is merely the ability to recognize your mistakes when you make them again.

 

[kandert]

You know... Requirment is just a purchase request form but my mind says: "Why not a notification for each request?". Okay somehow notification also done. Again my mind: "Approve, Abort features" would be nicer... I found that reflective journals https://www.nursingpaper.com/our-services/nursing-reflective-journal/ are a cornerstone of our learning process in nursing studies. When it comes to crafting effective entries, I've found a systematic approach to be beneficial. I start by selecting a particular patient interaction or clinical scenario that left an impact. Then, I delve into my thoughts and emotions during that experience, focusing on what I learned and how it influenced my understanding. Structuring my entry with an introduction, detailing the situation, delving into my feelings, and concluding with insights gained helps maintain a coherent flow. It's about capturing the essence of the moment and reflecting on how it contributes to my growth as a nurse.

I also like learning new things every day.

 

[kledo5]

It's a phenomena - I can't tell someone what I know until I'm asked, or if I have to solve a problem. Over time, an ability to solve a problem becomes - well - unsurprising; I assume that's 'master' level?

Show all.

 

[maksikasik]

super

 

[Isaac]

I will answer the title question.

You stop learning when you are dead. At which point you can only hope that others have learned from your examples.

For many people, their best example comes through their death itself. Many lessons to be learned from when and how people die.