Ask Experienced Devs Weekly Thread: A weekly thread for inexperienced developers to ask experienced ones

[-]

postnasal7459@reddit

For people who've worked in both the private and public sector as a swe:

Did you prefer working at a big tech company or for a federal contractor?
Would you say working for a federal contractor offers better job security, especially in this current market?
Is it hard to transition from the public sector to private?

[-]

Ok-Chair-7320@reddit

Hey folks,

How does the the market is currently for experienced devs ( 10+ years)?
how does it compare with 2024 and 2025?

[-]

Front-Opinion-9211@reddit

41 year old mid level vanilla php dev. I feel completely hopeless. My last role finished late 2025 - I've been learning AWS / basic DevOps - I vibe coded a django to Laravel ecs system.

It all seems so pointless.

I look at job roles wanting x years of React or Laravel to carry on with PHP.

I'd like out the tech rat race - but ai & tech seems to be everywhere

[-]

GnarlyHarley@reddit

How to build and release a large highly coupled domain with many windows services, APIs, uis and dbs.

[-]

casualPlayerThink@reddit

There is no silver bullet here. Every use case, project, company, and even region will answer this question absolutely differently.

I assume you are using some C#, which is why you would like to use Windows.

Move everything into containers, and hire a DevOps to discuss proper deployments. Usually expensive, but it will be worth the money.

Also, your host/provider (Azure?) should provide generic guidelines for deployment pipelines, builds, and releases. Might worth finding a consultancy that specializes in your ecosystem and in your area (so even personal meetup is possible).

[-]

GnarlyHarley@reddit

Thanks for the answer! I am curious about the everything in containers part.

Two questions: why everything containers?

How often do you run the containers locally when developing or do you just debug the project(s) without the container?

[-]

casualPlayerThink@reddit

Containers make it easier to enscapsulate and isolate the layers. Also, it would not pollute your actual host system, and easier to switch between versions. (Personal example: One of a project where I am contributing using 3 different node.js versions, 4 different database and 2 different php versions. Also one python and one golang. )

If something crashes, you can just rebuild a container. Near it, you can pull the repo on another device, and run the containers. No dependency install on host. And it guarantees every dev will have the same setup and run.

If I have a build/compiler container, then I run it every time, I have changed something and wanna test the changes. For node and php, I am usually start the containers at the start of my day, then the ecosystem runs and changes will be reflected because I am mounting the files usually, not copy them. So local docker could act as a VM. For react and other assets/frontend, usually I am rebuilding, recompiling via container calls, either by restart the container or just running a build container or just enter the container and running commands there. Quite depend on the project.

[-]

GnarlyHarley@reddit

Thanks for answering! Question was purely around build and release strategies. Such as conditional builds and releases potentially or utils,services and/strategies that help achieve that

[-]

Beginning_Basis9799@reddit

Start decoupling slowly and move to Linux.

[-]

The_Real_Slim_Lemon@reddit

Step 1: make those services run on Linux - otherwise you’ll hate yourself in a year

Step 2: build nothing manually, all infra through whatever IAC tool you prefer

Step 3: the earlier you get deployment pipelines the better

Step ??: unit tests need to run as a part of your deployment pipeline and/or your PR pipeline

Idk what else, but that’s my advice

[-]

Agitated_Ad_6939@reddit

Any general advice for a fresh grad starting their first non-internship SWE job?

[-]

naridax@reddit

How do y'all go about interviewing very experienced candidates? I have 9YOE, and I'll be interviewing someone with 27 lol...

[-]

SofaAssassin@reddit

What type of interview are you doing?

[-]

casualPlayerThink@reddit

It is fine. You are supposed to check why he/she is in IC still, as well as how they approach an issue, what mental models they are using, etc.

I have worked with companies, where they fear that I am too old and too experienced for my role (lead dev), because the rest of the company, altogether (6 ppl), had less experience in years than I. Eventually, I steered the ship, but the C* level/founders were adamant in their decision without critical thinking, so later they bankrupted the company (a few years after my contract ran its course).

[-]

pleasantghost@reddit

27 YOE wow

I also have 9. Some ideas:

If someone is much more experienced than you then it’s a good sign if you end up learning from them in the interview. Find a topic they can go deep on and keep asking questions until you are out of your league, they should be able to explain something new to you in a way you can understand

Also they should have some wisdom from their experiences. An interesting prompt may be to ask them something like “what are some things you’ve seen that appear to be new over time but you see as iterations of the same thing?”

They may be able to speak more to the whole end to end process of how an business uses engineering to accomplish its goals than just the dev side of things

I think with that much experience you should look for knowledge, wisdom, and mentor abilities. Not necessarily just chops

[-]

Maleficent-Serve5901@reddit

Do most companies involve 4+ interviews to get a dev job? I come from an industry with higher educational requirements than most developer jobs, and interviews even for the highest level jobs were like 2-3 interviews, for jobs that paid on average more.

[-]

casualPlayerThink@reddit

Unfortunately, yes. It is better now than before, around COVIDbig tech went really wild, and HN was full of 5-10 rounds of interviews, mostly because everyone copied the big tech/FAANG ways, which is ridiculous still

A few years back, I had these steps at one of the FAANG:
- HR preparation call (5-15m)
- HR clarification emails (bots)
- Blind coding test (solve X problem, leet-code\~ish, run unit tests but u won't see the tests, just the results; \~20m)
- Tech interview (defend your solution, \~30m)
- HR interview (20-30m)
- Tech interview with live coding (online 1h)
- Tech interview (personal, whiteboard tests, \~4-8h)
- Team fit interview (personal, full day at workplace)
- Contract interview (HR + tech lead; can be online; 1h)

And many companies copied this structure, so we ended up in 5-7 rounds for nothing, and it was pretty bad to sacrifice so many hours then not getting hired, not getting a project.
Now the number of interviews diminished, finally, but AI made the entire process quite... unpleasant. AI video interview and live coding sessions, where the bot ignores, repeats your solution, or repeats a task, then, at a clarification question, it starts to describe something completely irrelevant...)... ultimately, you have no control over that, they will use your answers and your video feed to train a GPT...

[-]

Maleficent-Serve5901@reddit

Holy. That's depressing. I had no clue they were doing AI video interviews. I guess I'll just stick to programming as a hobby...

[-]

JandersOf86@reddit

Im 40, work construction, but have been learning to program for about a year. C++ is my jam as it is the programming language that speaks to me, I guess, the most. I love the technicality and the intention of the language.

I've read a lot of comments regarding posting personal coding projects to github as a portfolio, and I've been doing that here and there. Some of the things I've found most enjoyable are creating sockets and packets from the ground up, and making programs like simple chat client/server programs, as well as cybersecurity related programslile simulated malware and network scanners, etc. All of these are written exclusively in C++.

I guess where I'm feeling pretty defeated is that I dont have a ton of extra time, with work and commuting and maintaining some down time when I can, and a lot of the job postings I see related to C/C++ often require knowledge of not only other languages but various other wrappers, APIs, things I havent ever touched. Frankly, I have choice paralysis when it comes to figuring out what other avenues to spend some time on that would potentially land me a gig doing what interests me. I only really have experience in C/C++ and basic version control with my own github. I kind of feel lost.

Some questions I have: - Is there a place, even if a niche / hyper-specialized place, for a position mostly involving C/C++ and socket creation and management, packet manipulation, more lower level network connection programming? What kind of positions would these be, and what kind of projects might I want to focus on further for my github portfolio for these positions? - With the endless choices of other languages, libraries, APIs, etc., which would be most beneficial for pursuing this kind of programming interest? Just looking for some direction in a sea of endless choices. - What kinds of products would need someone who specializes in what I think is essentially network programming? Is C/C++ considered outdated for these kinds of products or positions?

Any input would be much appreciated. Thanks in advance.

[-]

potatolicious@reddit

What you’re describing is systems programming or embedded programming. There are lots of places hiring C++ developers but I would encourage you to look at other languages popular within that realm (see: Rust). There’s a valid question here of if you like C++ because of something specific about that language or if you like it because it’s systems code.

Limiting yourself to just network programming is going to really restrict the jobs that are available to you. As a mid-career switcher it’s going to be an uphill battle to begin with so I would really strongly urge you to consider systems jobs as a whole and not specialize too early.

The types of jobs and companies you’re looking at are generally all device manufacturers of some sort. This can be a huge range: consumer electronics like phones, enterprise things like network gear, car electronics, etc. The field is quite wide.

My best advice to you is to start networking. There are fewer embedded and systems jobs than regular webdev, but also less competition. The scene is smaller and tends to hire a lot of referrals and recommendations.

[-]

JandersOf86@reddit

Thank you for the detailed response.

Regarding your point about why I like C++ (and Im not sure if this is a sufficient answer), I really like how intentional and spelled-out the syntax is. It's not that I automatically enjoy complexity for the sake of complexity but, for the purpose of understanding my own code, and code written by others, I like that it requires more detail because that detail gives more context and makes it easier for me to understand what is going on. A small example is declaring types, rather than the language inferring said types, or the use of semicolonsand curly braces to encapsulate functions / lines of code... I am not making any argument that these details / complexities make C++ "better" than any other language, but it simply makes it easier for me as the reader / doer of the code. More intentionality. I think I would like Java / JavaScript for the same reasons, I just haven't really spent a lot of time with JS. I dabbled in Python and did not enjoy it, but again I think it's just personal preference.

That being said, I'd be lying if I said I didn't also love the challenge of learning it when I've read / heard many other people say it's "difficult" and "shouldn't be your first programming language". I'll look into Rust, as you suggested.

Regarding general systems design, do you have any suggestions for learning projects that would maybe focus on those other areas ofnsystems design? I'm more than willing to admit my tunnel vision toward network programming.

Finally, when youre suggesting networking, I assume you dont just mean randomly adding embedded engineers on LinkedIn, right?

Thank you again for the response. It means a lot.

[-]

SofaAssassin@reddit

You are in the "I used a single language more than anything else and now it's the only one I think works" mode. What you've described doing could be done in a variety of languages - I have written networking code in C, C++, Rust, Perl, Python, C#, and Java.

And I say this as a person who's probably spent more years (in absolute terms) working in C++ than any other language, professionally. It is probably my "favorite" language but the work I've done with with it tended to be highly-specialized. And highly-specialized jobs also carry different expectations for things like interviewing, work and project expectations, and also just competition.

The best teams I've ever worked on/with and the best teammates I've ever had worked in C++, in that I was probably the stupidest developer on the team.

[-]

Whitchorence@reddit

I'm not a systems/embedded guy so I don't have first-hand knowledge. But I am a self-taught developer. Anyway, I'd say that: the thing about having to learn a lot of stuff besides just the programming language itself is common to any sub-field you might possibly decide to pursue, as is the fact that it just takes a lot of time to be good -- which is tough but necessary if you're trying to make it a career.

As for C/C++, generally you'd be looking at systems programming or embedded programming; the downside is, from what I can tell, there are usually fewer jobs and generally not as well compensated ones. But it's not my specialty at all so I don't want to give you bad advice.

[-]

JandersOf86@reddit

Thank you for the response. I'm definitely okay with the compensation being less if I'm doing something I'm enjoying, but the reduced jobs is obviously compounded by the state of the industry.

I appreciate the insight, either way.

[-]

joshocar@reddit

There are fewer embedded spftware jobs, but they are harder to fill. I had some small embedded projects on my LinkedIn for a while and would constantly get recruiters reaching out about embedded jobs.

[-]

JandersOf86@reddit

May I ask what kind of projects those were? I've been looking to get a raspberry pi and start needing around with that.

[-]

joshocar@reddit

I did a few small projects at my job. One was using, rs-232, SPI, and shift registers to control some relays. The other was interfacing with a temp/humidity sensor using i2C, and the last was sending some high frequency power data across a rs-232 line. All pretty simple stuff

Raspberry Pi development has some embedded parts to it, but isn't really embedded programming. Arduino is closer to embedded programming. Arduino hides a lot of the low level stuff, but it is a good starting point. Bare metal Arduino or getting a Cortex-M dev board (or one of the other main companies) would be a next step after Arduino.

[-]

JandersOf86@reddit

Awesome, I appreciate the Arduino suggestion, especially bare metal Arduino. And Ill look into some of those things you mentioned regarding your projects.

Thanks.

[-]

Administrative-Lack1@reddit

I am a full stack/ data engineering so take whatever I say with a grain if salt. This is just my surface lvl on the subject.

My best guess where this is used in today's tech world. Is embedded systems and firmware. A mix of hardware and software. Where you integrating a piece of hardware to connect to a network and controlling from code. I am sure there are more.

[-]

JandersOf86@reddit

I really appreciate the response, and the brutal honesty regarding the state of the industry, employment and layoffs.

Embedded systems with connecting hardware to a network sounds great. I will look further into this.

Thank you so much.

[-]

Administrative-Lack1@reddit

I will say. You may have more success if you shift to a more general coding position. Don't constrain your self into 1 niche field. These days you have to be able to do alot that use to be more of a specialized thing. For example front-end only devs getting phased out. You now have to be front end and backend at a minimum. Some places your doing front end, backend, db design, dev ops and that is being a full stack dev.

I will say, while still competitive fullstack web jobs are more "common" and you can always try to do more of a free Lance thing if you can get clients or use upwork, fiverr. Help design and build a website. It could be an alternative approach as a possible side thing.

It may not be exactly what your looking for but if you like coding in general. It could be something.

If your interested in web development.

React and Angular are popular front ends

Java (springboot), C# (.net), python (fast api, flask, django) are popular backend.

Also sql is a good (some would say must have) skill for backend.

I personally think react with Java and C# would be a good experience. But it's debatable. All theses things are just tools in your tool box. Choose the right tool for the right job.

But I do completely understand and respect if you don't have a interest in web stuff.

[-]

JandersOf86@reddit

Thank you for the advice. Honestly, front end web dev does not interest me in the slightest, but perhaps back end stuff might. Ill look into it.

Thank you again.

[-]

Whitchorence@reddit

Working on distributed systems/backend stuff might scratch some of the itch you have, or maybe I'm just biased.

[-]

almarcTheSun@reddit

I'll sidestep with a little hot take here, but especially if you're not a career C++ developer already and it's a hobby of yours, maybe look outside C++. C++ is a Frankenstein's monster of half-assed features added upon other half-assed features, rinse and repeat for 40 years.

Writing any other popular language, and I mean any other language even the ones that have a bad reputation such as PHP feels like driving a luxury car as opposed to C++, which feels like manually flying a space rocket that had buttons and features welded-on whenever there was empty space in the cabin for 40 years. If you know what you're doing then you're going to space. But it takes time and effort and if you all want is to drive around.. you get the idea.

Also, importantly - many C++ skills just don't carry over. Software is software, the concepts are the same. But the syntax and the implementation quirks aren't. C++ is a bit uh.. substandard in how it does things.

Rust is the relatively new popular kid on the block and it seems to genuinely be here to stay. The mean time between idea -> product is significantly slower or so I heard, but people seem to praise it almost unanimously. And also, try out other languages - C#, Java, Javascript, Go, Python. Just for fun, just to see how others roll.

I totally realize and respect that you said C++ is your jam, but respectfully with only a year of hobby programming at best you had enough time to only try out that one flavor somewhat properly.

[-]

JandersOf86@reddit

That is quite the hot take but I appreciate it nonetheless.

You're correct that I have not spent nearly the amount of time on any other language like I have with C++. I've dabbled a bit in Python, and spent a bit of time messing with C# and .Net MAUI. One of the major draws to C++ was that I do most of my programming in a Linux environment for Linux environments, and though C# has most of the same intentionality as C++, it seems, C# is more tailored toward Windows as far as I can tell. I'm not saying other languages can't be used for Linux/Unix but it seemed like C++ required the least amount of fuddling around to get it compiled, built and ran.

I appreciate your input. In another comment response above, you can read more of why I like C++, if you care to do so. That being said, I imagine youre correct that limiting myself is only going to do just that: limit myself.

Thanks for the hot take.

[-]

almarcTheSun@reddit

I'm really glad you're excited about it. I hope you keep at it and have lots of fun.

[-]

Crafty-Pool7864@reddit

Don’t pick a library to focus on. Pick a project you want to work on and work backwards to the right libraries for the job.

A good starting point is job listings. Don’t necessarily look at the list of libraries that may have been generated by HR. Find a C/C++ job, find the company/product associated with it, then work out what part of the system uses what and build a toy version. You’ll be surprised how quickly you can knock together an amateur version this way.

[-]

JandersOf86@reddit

That is a great strategy. I appreciate it and will do my best to implement it.

[-]

bestjaegerpilot@reddit

my only advice: there's no whining in software engineering

[-]

casualPlayerThink@reddit

Yes, this is somewhat true. Everyone should be super selective about where/whom/when to ventilate out the fumes, or who is the audience of the whining.

[-]

Real_nutty@reddit

Where do I find mentors? I have been leading a new project after 6 months into industry (fresh from undergrad); rebuilding an outdated inference pipeline for the team to build products on top of. No one really took their time to find alternatives and now that I built a faster (saved hours of compute time, $1M annual savings) alternative, expanding it and scaling it has been difficult since I do not have proper experience (I just know how to optimize these specific problems). Every month is another ask from the team and I pushback with technical requirements and infrastructure request which I gets taken seriously, but also the burden becomes larger the more I reject/redirect their request.

I wish I knew enough to know what to do in this case and also wish had enough “power” to influence headcount for this project instead of begging my manager for more help.

[-]

casualPlayerThink@reddit

Typically, a tech lead/lead dev, team lead, CTO, or senior would mentor you in this situation, since it seems you're handling tasks that someone higher up should take care of.

Not much you can do. If possible, start to discuss problems with DevOps to learn from it and get even just ideas and keywords, which will help approach it better. Might worth addressing these issues to someone higher up, above your manager.

I know this from experience, there are use-cases, when the manager just wanna solve things, does not care, it is not your expertise, or you have no ownership or decision-making power, yet all information must be dug up, begged for multiple times, and every task drags for extra days, weeks, or months just because of this.

[-]

Informal_Eye_148@reddit

I ran into something weird while trying to solve a problem I personally had as a dev.
Context switching + unclear task handoffs were slowing me down a lot, so I built a small internal tool to structure context before starting work (what to do, where to start, risks, etc.).

What surprised me:
managers immediately saw value in it,
but some devs were resistant.

Which confused me because… I built it for myself as a dev.
My current guess is: Anything that feels like “extra structure” gets interpreted as overhead/control, even if it actually reduces back-and-forth.
when does “helpful structure” start feeling like friction for you?

[-]

MindCrusader@reddit

Simple, it has to bring the value. If I get introduced to a new magic process that is supposed to help me, but I do not need it or it hinders my process, it is just wasteful. And a lot of managers love producing good sounding process slop.

Gather feedback from the devs what they do not like. What would they change

[-]

Informal_Eye_148@reddit

That makes sense.
Out of curiosity: when something *does* bring value for you, what does that actually look like in practice?
Like when you pick up a task:
- what’s your current way of getting context?
- what part of that process do you actually *not* want changed?
I’m trying to understand where tools usually cross the line from “helpful” -> “gets in my way”.

[-]

MindCrusader@reddit

We keep it as simple as possible: tickets from ClickUp have a lot of ACs. We break it out into parts if needed (UI, business logic, integration). Then create a PR per each subtask. Nothing more is needed for me, the tickets are in the sprint folder, we have tags indicating which version we aim for and just follow basic SCRUM.

The best processes are the simplest ones from my experience. If you overdo it, then nobody will want to follow them. They need to address the real issue and each new process should be an exception rather than something standard

[-]

Informal_Eye_148@reddit

That’s actually really helpful, I appreciate the clarity.
Sounds like your team already solves the problem at the source (strong ACs, clear breakdown), so there’s less need for something like this. What I’ve been seeing is teams where that doesn’t happen consistently, context lives in Slack, PRs, random discussions and the dev ends up reconstructing everything before starting. I think that’s where this kind of tool either clicks… or just feels unnecessary.

Thanks again. This helps me narrow down who this is actually for.

[-]

MindCrusader@reddit

Oh I know that. We just built a habit to keep the ACs in the tickets - ClickUp / Jira should be a single source of truth. It can also be in the comments of the tickets. If there is some issue discussed on slack, then it needs to have a ticket created. No ticket = no work will be done

[-]

Long_Drink1680@reddit

I work in a start up with the AI Team only consisting 3 engineers. We have a huge Enterprise AI project with roughly 12 sprints, and only 2 engineers are assigned to this. We have only been doing small scale automation and development projects so currantly we don't have CI/CD, automated testing, SOP documents or anything. I am planning on creating a PM plan, SOPs, setting CI/CD and using click Up for project management.

The major reason for this is that system is planned to use Plug-In architecture. If in the future, someone outside of the AI Team wanted to write a plug-in or fix a bug, that person would be in a tight spot. I should also mention that we usually manage our own projects and there's no PM in the company.

My question is would I just be over complicating things if I followed through like this or should I go ahead and do this?

[-]

dEstiNy_rUler@reddit

if i have an offer in hand, how do i negotiate with my current manager and org for an early release? do i mention that i have an offer or should i fake the reason?

[-]

AggressiveAd5248@reddit

You can just say you have a new offer and would like to cut short your notice by X months. They don’t necessarily want someone who isn’t motivated to be there, to be there, and you don’t want to be there.

You can also just leave, you aren’t a slave, some places have notice periods etc but at least in the UK the chances of someone taking you to court because you didn’t work your notice period - is really small.

[-]

shagieIsMe@reddit

You can also just leave, you aren’t a slave, some places have notice periods etc but at least in the UK the chances of someone taking you to court because you didn’t work your notice period - is really small.

The poster has posted in some of the India subs... and there are likely some complications based on that. https://workplace.stackexchange.com/questions/20945/what-is-a-relieving-letter-what-are-the-consequences-of-not-having-one

It's not a "they can't make him work" but rather "we didn't accept his resignation and his new employer can't hire him until he's been released."

[-]

dEstiNy_rUler@reddit

yeah man i have a notice period for 90 days, its such a trap, companies wont even interview candidates with 90 days NP and want someone immediately, but once they hire us the notice period will be 90 days. People say it depends on your reporting manager and how good your repo is with him, based on that he can either let you go early or he can make your life hell and make you beg to him to let us go

[-]

AggressiveAd5248@reddit

Ah, those kind of details are real important.

[-]

shagieIsMe@reddit

The phrasing of "early release" is something that tipped me off as a "this isn't likely a contract in the US" and go poke at the post history.

I'm likely glossing over a lot of the particulars of that law and relieving letters (it's things I've heard about)... but it can be a "not a simple situation" and the current employer could say "we don't care if you've got another offer, until we get another person in this contract and a week of knowledge transfer, you're still billable hours no matter how poorly you do and we're not providing you a relieving letter so you can start your next job."

[-]

DrSnakee95@reddit

I’ve been managing up for quite some time in my current position (been there 4 years) it seems I can’t stop myself from taking on things that are outside my scope and I’m starting to burn out. How do I set proper boundaries when management always explains away that it’s good I do more than I should? I’m worried about negative consequences

[-]

dfltr@reddit

Figure out how much you can do (measure your previous output) then keep a rolling window showing what’s currently on your plate and how much of it will realistically get done. Make sure everyone and their dog knows what’s in the Getting Shit Done Window and what’s out at any given time.

Whenever someone gives you more work, or asks to have their stuff bumped to the front of the queue, you say “Yes I’d love to do that, here’s where it fits in and here’s the other stuff that will get pushed out in order to get it done. Can you sign off on this priority change real quick?”

A whole lot of “urgent” projects get way less urgent as soon as they require a paper trail that leads back to someone other than you.

[-]

DrSnakee95@reddit

It sometimes seems like my manager does not want to make any decisions himself. He’s often asking us not to come with problems but with solutions, as well as pushing the burden of prioritising and planning. Ever experience something like this? I find it extremely hard to navigate as when he does do it, it’s done so badly that it impacts the entire team. It feels like weaponised incompetence at times.

[-]

Wide-Pop6050@reddit

So come to him with solutions. "We will be dropping XYZ to add ABC". It's like that rule of if you say something wrong on the internet someone will correct you.

[-]

Flashy-Whereas-3234@reddit

I'm an architect, I frequently pick up more than I can manage, I put it all on Trello and I have columns for "drop everything", in flight, next up, and backlog.

Backlog is where good ideas go to die. But they're still good ideas.

In my weekly 1:1 with my manager we go over what's been done and what is pending, if I'm smart enough I'll remember all the crap I picked up in the week, and I might pick up more stuff. Make no mistake, a good team has tickets and points and uninterrupted velocity and retros, and I have my chaos board.

The idea is to make it visual, to ensure you aren't just handed work and to make your workload a conversation.

If your manager is a piece of shit, you need to find ways to make yourself more visual in the company, ideally so your skip level can see you too. Push for doing internal workshops and reviews and grow the company culture. Go to lunch, go for beers, socialise around them with the rest of the business.

[-]

Success is about finding out what makes people want the same outcome as you, then making it happen.