|
As long as we are not talking natural disaster - then year many times, Singapore hotels weeks and months, serviced apartment for 9 months. Karratha a red spot on the pimple on the arse of Australia for 3 months in a donga (careful when you look that up). UK - 3 months in a rental near Slough.
Lots of us travel for work
Never underestimate the power of human stupidity -
RAH
I'm old. I know stuff - JSOP
|
|
|
|
|
Two 7-week stints and a 2-week stint in Bangalore, and two week-long stints in Vienna, all enjoyable.
|
|
|
|
|
Slow Eddie wrote: your own
I would love living at the ocean, because I love about everything there (The sea, the wind, the smell, the salt, the sand, the landscape, the sunsets or rise, swimming in the morning and in the evening, kayak, paddle,...). Not possible for the next 30 years, because Mrs.Rage would not move far away from her family (by her definition, "far" is "more than 100m") - but this would be my place. So I have had to stay in a place other than mine for more than 40 years now.
|
|
|
|
|
Slow Eddie wrote: Been living in a hotel in Gulf Shores AL
Slow Eddie wrote: HOWEVER, I can't wait to get back home
But..., sweet home is only Alabama.
"In testa che avete, Signor di Ceprano?"
-- Rigoletto
|
|
|
|
|
Slow Eddie wrote: HOWEVER, I can't wait to get back home. I went on the web to the power company's site map of which parts of the city have power restored and my neighborhood. Not sure if I can trust them or not. SWMBO does not and wants to stay another week! Never mind the cost.
Drive home by yourself to check that power is back, internet is back, and your home is habitable: If yes to all return to the hotel and check out with SWMBO. If no, be glad you didn't give up your hotel room.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
|
|
|
|
|
I've traveled for work over the last 20 years or so. At times I've stayed at hotels for two to three weeks at a time coming home for a few days and heading out again. Usually though it's for much shorter periods. My wife made that possible by being home for the kids when I couldn't.
The worst time a way from home was after a fire that took out seven homes in our block. We stayed with family and friends for a few days at a time until the insurance started covering a hotel. It was about four weeks in the room until we found a suitable house to rent, we weren't going to be able to go back home anytime soon.
The biggest weirdness was knowing that we and our neighbors suffered a "tragedy", but the familiar world around us was going on as normal. Seeing news stories about the hurricanes and fires that wipe out large areas are so much greater than what we had experienced as we could still buy gas and groceries and get around. We just had no place that was "home".
The fire happened in 2008 on the Monday before U.S. Thanksgiving. I remember reading an article Thanksgiving morning in the local paper about people being thankful. One story was about another fire that happened several years before. The guy they were interviewing said something like, "It takes time to get back to normal. Everything about your daily life is going to be different for awhile. But slowly you get back to it."
He was right. All is well now. We were able to get away from a deteriorating neighborhood and with a job change live in a different state. But I never view news about families losing their homes the same way again. When there is a donation can out, I rarely pass it by without making a donation.
|
|
|
|
|
Displicines f1 -> (?) Code Monkeys
------------------ -------- ------------
1 2 ... N ? Available
How do we solve transition f1=(Discipline) to code?
I mean there are lot of qualified (web) programmers but they only know how (hopefully) to implement a nice GUI, but they do not have (and are not willing/able to get) any idea about the business...
modified 4-Oct-21 21:01pm.
|
|
|
|
|
Use a big stick.
Works for me.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
I stick on that
modified 4-Oct-21 21:01pm.
|
|
|
|
|
Beats Me
ed
|
|
|
|
|
Member 15347602 wrote: but they only know how (hopefully) to implement a nice GUI That's a hell of an assumption, and a hope I would not have. But maybe you have done a crap job of hiring... If so, maybe f1 = fire crap programmers and start over.
|
|
|
|
|
Quote: That's a hell of an assumption
I'm not writing about 'one man shows' which I assume you are in
It's more about enterprise company things.
modified 4-Oct-21 21:01pm.
|
|
|
|
|
Member 15347602 wrote: It's more about enterprise company things.
Not sure what that means but....
Large companies always trend toward the average. At best.
|
|
|
|
|
Unless your business is a common one, you always have to train incoming personnel in the domain knowledge they need to know in order to do their jobs. This includes developers.
Expecting them to know a priori 'the business' is naive at best. Your 'code monkey' term indicates an attitude of contempt toward your coworkers, which doesn't help matters.
Teaching them what they need to know would be more useful.
Software Zen: delete this;
|
|
|
|
|
Gary R. Wheeler wrote: you always have to train incoming personnel in the domain knowledge
I have often said the same. It is better to retain staff ond upskill them on technical knowledge than to use what HR call 'fresh blood' with the technical skill but without history on how their particular organisation ticks. Technical domain skills are (in theory) easy to acquire; but business domain is specific to an organisation and cannot be simply bought in. Business domain include how the organisation works and how the code base that supports it works; they are one-offs, even if the organisation is using an industry standard package. I've been in my current job for over 5 years and there are huge swathes of the business side that I have not fathomed (especially their software base).
|
|
|
|
|
Member 15347602 wrote: but they do not have You are making some wild assumptions there. Or maybe your recruitment ads need some work. Either way it is easy to see where the problem is.
|
|
|
|
|
Member 15347602 wrote: any idea about the business In my opinion, it's the business' job to know about the business.
I should know just enough to do my job, but I should be told so by... Yes, the business.
You can't expect a developer to know about programming and everything related (databases, cloud, networking, etc.) and also know everything about whatever business you're working in (if it's even the same as a developer's previous job(s)).
Even if I know about some domain, let's say transport, every transport company probably has their own way to do things.
I could make something amazing that would've worked wonderfully at another business, but not yours.
Now go ask "the business people" if they know what their neighbor does, they don't.
Sales doesn't know accounting doesn't know planning doesn't know IT...
Yet people expect developers to know about all of them
|
|
|
|
|
But you're talking about "developers". IT is about a lot more than "coding" (which I think the original questioner implied through the term "code monkeys"). There used to be disciplines (that word again) such as business analyst, systems analyst etc and I'm sure there still are. It's their job to understand the business and its requirements, and translate that into systems requirements for the developers to build.
The other issue is that "knowing the business" in the original context mentioned above (i.e. knowing about, say, "logistics") is useful but if every developer in that industry knows generic "logistics", then there is no innovation, no USPs, no advantage.
As a "full stack" freelancer I'm constantly trying to not only learn my client's business, but bring knowledge and ideas from other industries (clients) together with new technology-related ideas and concepts to try and give the client that innovation and advantage. It gets frustrating when the client tells me too precisely what they "want" and doesn't involve me in their business processes - it's like having my hands tied and I know I can't bring the added value I'd like.
So to address the original question - it may be that the environment in question is too developer-heavy, and actually needs some business analysts to act as a channel for business requirements to get converted into development specs. Failing that, if it's a small site that can't justify multiple roles, get the developers on some business analysis and systems design courses.
|
|
|
|
|
DerekT-P wrote: But you're talking about "developers". So did the OP, although he called them "code monkeys".
DerekT-P wrote: There used to be disciplines (that word again) such as business analyst, systems analyst etc and I'm sure there still are. I've worked with them, so they're still around.
DerekT-P wrote: As a "full stack" freelancer I'm constantly trying to not only learn my client's business, but bring knowledge and ideas from other industries (clients) together with new technology-related ideas and concepts to try and give the client that innovation and advantage. It gets frustrating when the client tells me too precisely what they "want" and doesn't involve me in their business processes - it's like having my hands tied and I know I can't bring the added value I'd like. Agreed on everything you said, though I wouldn't call you, or me, a code monkey.
And technically, we're not just developers either.
I do like my client to tell me exactly what they want, and then I can go about and tell them how I'm going to do it.
When the customer starts to tell me about the how, I get annoyed, because that's them telling me how to do my job.
DerekT-P wrote: Failing that, if it's a small site that can't justify multiple roles, get the developers on some business analysis and systems design courses. Exactly, I've worked for such a company.
Except we didn't get courses, we just went to the client, had some meetings, and started building.
Any questions were asked directly to the client, as we ran into them, by phone or email.
It was pretty ad-hoc, which is how I still do most of my coding
|
|
|
|
|
DerekT-P wrote: I'm constantly trying to not only learn my client's business, but bring knowledge and ideas from other industries (clients) together with new technology-related ideas and concepts to try and give the client that innovation and advantage So did I... but that came with experience and not learning the business of my next project in advance...
Specially when my next project was assigned to me, and then to be started in a couple of days (at best yesterday).
DerekT-P wrote: It gets frustrating when the client tells me too precisely what they "want" and doesn't involve me in their business processes - it's like having my hands tied and I know I can't bring the added value I'd like. I had a customer that was like that and yes, I give you that it is frustrating. But most of the "business" doesn't know enough about our business to really know if you are doing the things in a way or in another (as long as there is not visible change in the outside)
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
That's consultant thinking.
Or are you implying that programmers aren't part of the business?
|
|
|
|
|
Depends, I've never felt myself a part of the business as I'm always just an external programmer.
I'm part of a business, just not the customer's
|
|
|
|
|
In my personal experience, programmers are often the people with the best understanding of how the business actually works.
But that is obviously depending on the size of the company and probably isn't true for companies where IT is of secondary importance.
In short, mileage will vary.
|
|
|
|
|
That's a scary thought though...
Can you imagine how little the average person knows about their job?
I've certainly met people who "press this button, which does stuff."
|
|
|
|
|
I know.
And guess who programs that button.
|
|
|
|