|
I've never hated it but my first job did frustrate me sufficiently that I quit. I liked my coworkers but they weren't properly trained so it was really tough trying to get anything developed there. They also had quite strict working hours which I don't do all that well with (particularly in the weeks after the clocks going on!).
It's a good company, but it didn't work out for me there.
You can never expect everything to be perfectly fun at work, though – if something's that fun then you don't have to pay people to do it.
|
|
|
|
|
Whenever we work under pressure with tight schedules,there is a my co-worker who is Functional Analyst, laughs and says "That's why I have not chosen Development."
___ ___ ___
|__ |_| |\ | | |_| \ /
__| | | | \| |__| | | /
|
|
|
|
|
Yes, one time at the same place.
We had a top-notch contractor in, because he cost ££££s (which he actually earned - I've heard horror stories about countractors) they actually listened to him and he turned the outfit into a dynamic and interesting place to work. He left and the lessons weren't learned by the people making the decisions, so we went back to the moribund default state.
All it takes quite often to flip from one state to another is one person to enter or leave the team.
|
|
|
|
|
It usually takes both the people and the job together for me to hate the job. If the job is great but the people aren't, I can work with that. If the people are great but the job sucks, then I find value in that. But both? Ugh. I left a job after one week recently because of that combination (mind you, two of the three people were great, but the important person, the PM, was awful, and he's the one that counted.)
Marc
|
|
|
|
|
I started at a new company 3 weeks ago and I'm considering leaving. They're too busy to give me something to sink my teeth into, and not being productive makes me utterly miserable.
Even a bad project is better than being forced to try and look busy because you're new at the job 
|
|
|
|
|
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
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
