There are numerous cars from about a decade (+/-) ago, that would satisfy these requirements broadly. However, you don't say whether you're looking for an SUV, sedan, runabout, etc.
Price range, brand preference, location also play a role.
2,736 karma · joined February 15, 2012
There are numerous cars from about a decade (+/-) ago, that would satisfy these requirements broadly. However, you don't say whether you're looking for an SUV, sedan, runabout, etc.
Price range, brand preference, location also play a role.
Perhaps try looking at https://www.seek.com.au/, https://www.indeed.com.au/, etc.
Best guess based on anecdata, however, suggests doctor, even factoring in length of studies, community service/internship, etc - they really start ramping up quickly once you're all qualified, and especially if you keep on advancing your career.
Now, if you wanted to talk about getting spammed/scammed after registering a domain with Godaddy...
GP: Could you post some information on the issues with containers?
[1] https://zulip.readthedocs.io/en/stable/production/install.ht...
Regarding electron/react native - no worse than Slack, I guess (as far as resource usage, etc goes).
Agreed that portability beyond these platforms is a different story altogether.
https://www.premier.vic.gov.au/shining-a-light-on-flinders-s...
Any particular reason you prefer open source (considering Jetbrains' tools aren't)?
What's your preferred platform?
- Can I still buy those from amazon.com, or will I need to get them from amazon.com.au?
- If I need to buy from amazon.com.au, will that be subject to the same substantially reduced variety/options available?It doesn't do calendar integration (which probably makes it slightly off-topic), but for a lot of the other items mentioned in general note taking posts below, it works fantastically well.
I haven't used Java in a while, but my experience lately with Python docs (both formal and informal) has been fantastic. This applies not just to the core language and libraries, but also various third party libraries and frameworks.
For the first:
- Do your research
- Know what you need (vs what you might want)
- Know what you can pay (conservatively, and at a maximum)
- Don't be afraid to say no
- Don't be afraid to ask questions
- Never feel pressured into a transaction - go away and think/process things
For the second:
- Don't be afraid to immediately tell them you're not interested (in fact, you should do this by default if it's something you don't need)
- Know your finances, so that you're aware of what you can and can't afford (this might be impetus to cut off the call sooner rather than later)
- If it's something you may need, or have looked at, the points above apply
An interesting thing I've discovered (anecdata) - salespeople are wary of engineers, because we rarely take something at face value. If you are one, make sure they know this early on (either state it, or make sure they know you know something about the domain). In the past it's done two things for me:
- The sales person is less likely to make wild claims, and will be more careful to make statements that can be backed up
- Often, they become less pushy, because they know they will have to work for the sale (rather than rely on emotion and ignorance)
One last comment: don't mistake courtesy for friendliness. Sales people are there to do a job. They are not your friends (you don't owe them anything), and it's the exception to the rule that they will have your best interests at heart. Keep this in mind while you're talking to them.