In order to fix the problem, utilize the said person's name. Simply prefix the function names with him/her.

Suppose said person was 'Jane'.

function Jane_DataValid(data: string): boolean;
begin
  if string = ' ' then 
  begin
     result:= false;
     exit;
  end;

  if string = '' then 
  begin 
    result:= false;
    exit;
  end;

  result:= true;
end;

procedure Jane_ParseData(s: string);
var i: integer;
begin
  if not Jane_DataValid(s) then exit;
  i:= 1;
  while i < length(s) do
  begin
    inc(i);
    // simple quote finder
    if i = '"' then 
      if inquote then inquote:= false else inquote:= true;
    // other nonsense, not optimized
    if inquote then 
      quotebuf:= quotebuf + s[i]; 
  end;
end;

The productivity of a project is directly linear to the success of subject which is on the mind of the programmer. If the programmer does not embed said person in each and every function (or module name/unit name) somewhere, the programmer will simply not be productive. The programmer will wander off writing poems/notes to the said person instead of writing code for the project.

Embedding source code poems inside the files at the bottom, top, or in the middle of the file about said person is also permitted ocassionaly - but not to go as far as allowing the programmer to write more poems than source, since the code should be the poem the programmer is reading (and having said lover do things for him in the code such as Jane_ParseData allows programmer to feel wonderful about said person since she is obviously helping in parsing stage of the project - the code says so itself and shall not be disputed).

If other developers on the team question, resist, or shout at you for embedding said person in the functions, ask them if they want the work done, or if they want nothing done.

If multiple developers have different said persons on mind, certain files must be dedicated to each said lover. Example: miscutils dedicated to person1, netutils dedicated to person2.

Today's Lesson

If the programming language being used has namespaces, modules, or units available, it is acceptable to instead embed the said person into the module name, namespace, or unit name instead of always using Prefix_Style syntax.

unit JaneNetUtils

interface
  function PortValid: string;
  function IpValid: boolean;

implementation

function PortValid: string;
begin
  // code...
end;

function IpValid: boolean;
begin
  // it is essential to reference said person more than once each source file
  if JaneMiscUnit.IsEmpty(s) then exit;
  // code...
end;

end

As the name trickles through the modules, units, code, namespaces, etc. the said lover will sprinkle the source reminding the programmer to focus on the code since the code requires the said lover to be typed over and over again in different places. There is no hesitation to program, because the more coding that is done, the more the lover ends up showing up in the code and helping the project along.

It is not enough just to name the entire project after the said person, or code name the project after the person - because programmers don't read the project name, programmers read the code. Programmers need the said lover to help out in the project some way. Otherwise, the project is doomed.

Extreme Circumstances Not in Your Control