|
Ri_ wrote: Even a bad project is better than being forced to try and look busy because you're new at the job
That's one of the reasons why I left the job after a week. I was told to bill 40 hours a week. There wasn't the work to support that. I don't mind fudging a little (after all, one ends up putting in 70+ hours sometimes) but this was absolutely ridiculous.
Still, gift horse and all that. I just couldn't ethically do it though. 
Marc
|
|
|
|
|
Marc Clifton wrote: I just couldn't ethically do it though.
Ethics! Sucks to have them  I wonder if it skips a generation because sometimes seems as if it missed the Millennials.
|
|
|
|
|
It's not the people I work with that annoy me. It's the few customers who seem to call multiple times every week with the oddball scenarios that need special attention that make me hate the job sometimes...like today. 
"Go forth into the source" - Neal Morse
|
|
|
|
|
I work in this place with a guy called
Member 9244203 and he makes me hate my job 
|
|
|
|
|
|
I hate my job but not because of the people I work with. I hate it because of the totally asinine coding rules that I am forced to comply with. Team lead is a nice person but bullheaded and claims the customer we work for will not permit any changes to the rules for us but yet the customer regularly ignore their own rules.
modified 30-Apr-21 21:01pm.
|
|
|
|
|
It's not just you - some people who work alone feel the same way.
|
|
|
|
|
Sometimes I felt bored of my workplace.
Programmer is only me and other people are sales and management.
I'm younger in my team and sometimes my worker is too old.
It's hard to communicate with them.
I have been worked for 3 years in window programming..
Thesedays, I got slump and lose interest.
|
|
|
|
|
what do you call a sting that holds a file path together with the file name itself
e.g. C:\Folder\Directory\myFile.txt
And what do you call just the file name?
e.g. myFile.txt
And what about just the name of the folder the file is in?
e.g. C:\Folder\Directory
I never seem to be consistent - I think we need a new word (or am I missing something?)
|
|
|
|
|
Filepath:
C:\Folder\Directory\myFile.txt
Filename:
myFile.txt
Folderpath, or path:
C:\Folder\Directory
<br />
Folder
Directory
~RaGE();
I think words like 'destiny' are a way of trying to find order where none exists. - Christian Graus
Entropy isn't what it used to.
|
|
|
|
|
This is good 
|
|
|
|
|
Rage wrote: Filename:
myFile.txt
I would change that slightly:
FileName:
myFile
Complete Filename:
myFile.txt
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952)
Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
|
|
|
|
|
_Maxxx_ wrote: e.g. C:\Folder\Directory\myFile.txt
filePath as it is the path to the given file
_Maxxx_ wrote: e.g. myFile.txt
file
_Maxxx_ wrote: e.g. C:\Folder\Directory
path
|
|
|
|
|
_Maxxx_ wrote: e.g. C:\Folder\Directory\myFile.txt
Path
_Maxxx_ wrote: e.g. myFile.txt
File or filename
_Maxxx_ wrote: e.g. C:\Folder\Directory
Folder or directory
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
|
|
|
|
|
Kornfeld Eliyahu Peter wrote: Folder or directory
A good example of nuance I've never really gotten.
~RaGE();
I think words like 'destiny' are a way of trying to find order where none exists. - Christian Graus
Entropy isn't what it used to.
|
|
|
|
|
Originally folder is a logical term where used much before computers, where directory is the physical place on the storage and came to use with computers...
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
|
|
|
|
|
There is no folder; only directories.
You'll never get very far if all you do is follow instructions.
|
|
|
|
|
_Maxxx_ wrote: C:\Folder\Directory\myFile.txt
filename
_Maxxx_ wrote: myFile.txt
filename
_Maxxx_ wrote: C:\Folder\Directory
path
The first two are basically the same thing: both of them let you find a file. One is relative and one is absolute but in most cases you don't care about that. I/O methods will accept either and do the right thing.
If you do care then I'd call the first either filePath or absoluteFilename.
|
|
|
|
|
BobJanova wrote: he first two are basically the same thing
Nonsense
BobJanova wrote: I/O methods will accept either and do the right thing
Lordy lord, what sort of systems are you working on?
|
|
|
|
|
You forgot relative path, for example: ./bin/debug
Marc
|
|
|
|
|
_Maxxx_ wrote: And what about just the name of the folder the file is in?
They aren't folders they are directories. It should still be called FileManager, not Windows' Explorer.
A pox upon whoever made those UI decision.
|
|
|
|
|
Absolutely. Directories are EXACTLY right, as the directory is jsut a collection of pointers to the files within - whereas the folder metaphor implies the physical existence of the files within the folder, which is drivel and rot.
If anything, a disk drive should be a folder, containing directories of files.
But we are victims of the dumbing down of It and, in most cases, it doesn't matter to the user who (lets be honest) call their monitor their computer and the computer their hard drive!
|
|
|
|
|
Exactly! Also More Like An Index Or Catalog. A Document May have links From Many Directories. Try That With Folders!!
You'll never get very far if all you do is follow instructions.
|
|
|
|
|
In my code, filename means just the filename (and extension); pathname means the entire path including filename. The path is just the path.
|
|
|
|
|
You call them all a path. Then you have methods to tell you which bits they include. Look at the dot net System.IO.Path namespace.
If you can work the word 'Rooted' in there somewhere you are doing really well.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
