Althoughcertain symptoms are common with specific mental health problems, no two people behave the same way when unwell. You may notice changes in their behaviour or mood if you know the person well.
It can be challenging to know what to do if you are worried about someone. When you know there is an issue, it is essential not to wait. Waiting and hoping they will come to you for help might lose valuable time getting them support.
Discuss ways of de-stressing or practising self-care and ask if they find anything helpful. Exercising, having a healthy diet and getting a good night's sleep can help protect mental health and sustain wellbeing.
Remember that If you believe they are in immediate danger or have injuries that need medical attention, you must take urgent action to ensure they are safe. More details on dealing in a crisis can be found below.
If it is a family member or close friend you are concerned about, they might not want to talk to you. Try not to take this personally: talking to someone you love can be difficult as they might be worried they are hurting you. It is important to keep being open and honest and telling them that you care. It may also be helpful to give them information about organisations or people they can reach out to. A list can be found below.
You can ask how they feel and let them know you are available to listen. Talking can be a great help to someone who is feeling suicidal, but it may be distressing for you. You need to talk to someone about your feelings; the Samaritans can help you.
If they are planning to take their own life, please encourage them to call 999 (UK) or go to A&E and ask for the contact of the nearest crisis resolution team. These are teams of mental health care professionals who work with people in severe distress.
The first person to approach is your family doctor. they should be able to advise about treatment and may refer you to another local professional. See our guide on How to talk to your GP about your mental health.
Several specialist services provide various treatments, including counselling and other talking treatments. Often these different services are coordinated by a community mental health team (CMHT), which is usually based either at a hospital or a local community mental health centre. Some teams provide 24-hour services so that you can contact them in a crisis. You should be able to contact your local CMHT through your local social services or social work team.
Mind provides information on a range of mental health topics to support people in their own area from 9.00 am to 6.00 pm, Monday to Friday. Call 0300 123 3393 or email [email protected].
If you are feeling like ending your life or feel unable to keep yourself safe, please call 999 or go to A&E and ask for the contact of the nearest crisis resolution team. These are teams of mental health care professionals who work with people in severe distress. If you feel affected by the content you have read, please see our get help page for support.
There are companies which create software which actually gets used by customers, which describes almost everything that you probably think of when you think of software. It is unlikely that you will work at one unless you work towards making this happen. Even if you actually work at one, many of the programmers there do not work on customer-facing software, either.
Engineers are hired to create business value, not to program things: Businesses do things for irrational and political reasons all the time (see below), but in the main they converge on doing things which increase revenue or reduce costs. Status in well-run businesses generally is awarded to people who successfully take credit for doing one of these things. (That can, but does not necessarily, entail actually doing them.) The person who has decided to bring on one more engineer is not doing it because they love having a geek around the room, they are doing it because adding the geek allows them to complete a project (or projects) which will add revenue or decrease costs. Producing beautiful software is not a goal. Solving complex technical problems is not a goal. Writing bug-free code is not a goal. Using sexy programming languages is not a goal. Add revenue. Reduce costs. Those are your only goals.
Instead, describe yourself by what you have accomplished for previously employers vis-a-vis increasing revenues or reducing costs. If you have not had the opportunity to do this yet, describe things which suggest you have the ability to increase revenue or reduce costs, or ideas to do so.
There are many places to meet people. Events in your industry, such as conferences or academic symposia which get seen by non-academics, are one. User groups are another. Keep in mind that user groups draw a very different crowd than industry conferences and optimize accordingly.
In general, big companies pay more (money, benefits, etc) than startups. Engineers with high perceived value make more than those with low perceived value. Senior engineers make more than junior engineers. People working in high-cost areas make more than people in low-cost areas. People who are skilled in negotiation make more than those who are not.
f) Read a book. Many have been written about negotiation. I like Getting To Yes. It is a little disconcerting that negotiation skills are worth thousands of dollars per year for your entire career but engineers think that directed effort to study them is crazy when that could be applied to trivialities about a technology that briefly caught their fancy.
Because you radically overestimate the likelihood that your startup will succeed and radically overestimate the portion of the pie that will be allocated to you if the startup succeeds. Read about dilution and liquidation preferences on Hacker News or Venture Hacks, then remember that there are people who know more about negotiating deals than you know about programming and imagine what you could do to a program if there were several hundred million on the line.
The high-percentage outcome is you work really hard for the next couple of years, fail ingloriously, and then be jobless and looking to get into another startup. If you really wanted to get into a startup two years out of school, you could also just go work at a megacorp for the next two years, earn a bit of money, then take your warchest, domain knowledge, and contacts and found one.
Working at a startup, you tend to meet people doing startups. Most of them will not be able to hire you in two years. Working at a large corporation, you tend to meet other people in large corporations in your area. Many of them either will be able to hire you or will have the ear of someone able to hire you in two years.
So would you recommend working at a startup? Working in a startup is a career path but, more than that, it is a lifestyle choice. This is similar to working in investment banking or academia. Those are three very different lifestyles. Many people will attempt to sell you those lifestyles as being in your interests, for their own reasons. If you genuinely would enjoy that lifestyle, go nuts. If you only enjoy certain bits of it, remember that many things are available a la carte if you really want them. For example, if you want to work on cutting-edge technology but also want to see your kids at 5:30 PM, you can work on cutting-edge technology at many, many, many megacorps.
Your most important professional skill is communication: Remember engineers are not hired to create programs and how they are hired to create business value? The dominant quality which gets you jobs is the ability to give people the perception that you will create value. This is not necessarily coextensive with ability to create value.
You will often be called to do Enterprise Sales and other stuff you got into engineering to avoid: Enterprise Sales is going into a corporation and trying to convince them to spend six or seven figures on buying a system which will either improve their revenue or reduce costs. Every job interview you will ever have is Enterprise Sales. Politics, relationships, and communication skills matter a heck of a lot, technical reality not quite so much.
When you have meetings with coworkers and are attempting to convince them to implement your suggestions, you will also be doing Enterprise Sales. If getting stuff done is your job description, then convincing people to get stuff done is a core job skill for you. Spend appropriate effort on getting good at it. This means being able to communicate effectively in memos, emails, conversations, meetings, and PowerPoint (when appropriate). It means understanding how to make a business case for a technological initiative. It means knowing that sometimes you will make technological sacrifices in pursuit of business objectives and that this is the right call.
All business decisions are ultimately made by one or a handful of multi-cellular organisms closely related to chimpanzees, not by rules or by algorithms: People are people. Social grooming is a really important skill. People will often back suggestions by friends because they are friends, even when other suggestions might actually be better. People will often be favoritably disposed to people they have broken bread with. (There is a business book called Never Eat Alone. It might be worth reading, but that title is whatever the antonym of deceptive advertising is.) People routinely favor people who they think are like them over people they think are not like them. (This can be good, neutral, or invidious. Accepting that it happens is the first step to profitably exploiting it.)
I am new to HubSpot and in the process of setting up Deals (with three pipelines)-for capital equipment, service contracts and disposable products. The first two (capital contract and service pipeline deals) are easy since they are one time "deals" lasting year(s). But I am looking to find others that have Sales Hub Professional that have determined how to handle "recurring sales" in deals for disposable products (without having Enterprise version). Do you enter every transaction as a deal, proactively or when you get the invoice?
3a8082e126