Best Binary Options Apps For Mobile Trading 2020

Facebook Connect / Quest 2 - Speculations Megathread

EDIT: MAJOR UPDATE AT BOTTOM
Welcome to the "Speculations" mega thread for the device possibly upcoming in the Oculus Quest line-up. This thread will be a compilation of leaks, speculation & rumors updated as new information comes out.
Let's have some fun and go over some of the leaks, rumors, speculation all upcoming before Facebook Connect, we'll have a full mega thread going during Connect, but this should be a great thread for remembrance afterward.
Facebook Connect is happening September 16th at 10 AM PST, more information can be found here.

Leaks
In March, Facebook’s public Developer Documentation website started displaying a new device called ‘Del Mar’, with a ‘First Access’ program for developers.
In May, we got the speculated specs, based off the May Bloomberg Report (Original Paywall Link)
• “at least 90Hz” refresh rate
• 10% to 15% smaller than the current Quest
• around 20% lighter
• “the removal of the fabric from the sides and replacing it with more plastic”
• “changing the materials used in the straps to be more elastic than the rubber and velcro currently used”
• “a redesigned controller that is more comfortable and fixes a problem with the existing controller”

On top of that, the "Jedi Controller" drivers leaked, which are now assumed to be V3 Touch Controllers for the upcoming device.
The IMUs seem significantly improved & the reference to a 60Hz (vs 30hz) also seems to imply improved tracking.
It's also said to perhaps have improved haptics & analog finger sensing instead of binary/digital.
Now as of more recent months, we had the below leaks.
Render (1), (2)
Walking Cat seems to believe the device is called "Quest 2", unfortunately since then, his twitter has been taken down.
Real-life pre-release model photos
Possible IPD Adjustment
From these photos and details we can discern that:
Further features speculation based on firmware digging (thanks Reggy04 from the VR Discord for quite a few of these), as well as other sources, all linked.

Additional Sources: 1/2/3/4
Headset Codenames
We've seen a few codenames going around at this point, Reggy04 provided this screenshot that shows the following new codenames.
Pricing Rumors
So far, the most prevalent pricing we've seen is 299 for 64gb, and 399 for 256GB
These were shown by a Walmart page for Point Reyes with a release date of September 16 and a Target price leak with a street date of October 13th

Speculation
What is this headset?
Speculation so far is this headset is a Quest S or Quest 2
OR
This is a flat-out cheaper-to-manufacture, small upgrade to the Oculus Quest to keep up with demand and to iterate the design slowly.
Again, This is all speculation, nothing is confirmed or set in stone.
What do you think this is and what we'll see at FB Connect? Let's talk!
Rather chat live? Join us on the VR Discord
EDIT: MAJOR UPDATE - Leaked Videos.
6GB of RAM, XR2 Platform, "almost 4k display" (nearly 2k per eye) Source
I am mirroring all the videos in case they get pulled down.
Mirrors: Oculus Hand Tracking , Oculus Casting, Health and Safety, Quest 2 Instructions, Inside the Upgrade
submitted by charliefrench2oo8 to OculusQuest [link] [comments]

# /r/Peloton Pre-TDF Survey 2020

Gentlemen, Ladies and those otherwise addressed - we know you've been waiting for a good thing, and the survey results are finally ready!
The answers were collected from you all during August 2020 with 1428 unique replies. That's a participation of 0.5% of all subscribers! That's really not too bad, when you keep in mind how popular these kind of surveys are. But we here at /peloton want to show you that this is all about presenting the information in the subreddit to cater better to our audience!
Updated after a few hours to include some more historical data the final edit that for some reason wasn't copied properly
Year 2013 2014 2015 2016 2018 Mar 2018 Aug 2019 2020
Results 2013-06-12 2014-06-25 2015-08-07 2016-11-17 2018-03-06 2018-08-20 2019-07-22 2020-10-12
Replies 351 598 1395 892 630 928 986 1428
Without further ado, let's get cracking on the response

You and Cycling

1. Where do you live?

Country 2015 2016 2018 Mar 2018 Aug 2019 2020
USA 32% 28.3% 22.84% 25.32% 20.23% 24.59%
UK 18.6% 17.6% 14.70% 20.13% 15.48% 14.80%
Netherlands 6.4% 9.4% 11.50% 11.58% 10.01% 11.01%
Germany 3.73% 3.4% 4.95% 6.39% 7.84% 6.65%
Denmark 3.9% 3.6% 4.31% 3.79% 7.64% 5.79%
Belgium 3.8% 2.7% 8.15% 3.57% 5.78% 5.36%
France 2.01% 1.08% 2.88% 2.27% 5.26% 3.50%
Canada 4.9% 7% 6.39% 4.22% 4.95% 4.50%
Australia 5.2% 4.7% 3.83% 4.00% 4.33% 3.93%
Slovenia 0.73% 0.32% 1.30% 1.14% 2.14%
Norway 2.58% 1.8% 1.60% 1.95% 2.58% 1.86%
Sweden 1.08% 1.09% 1.44% 1.41% 1.75% 1.43%
Ireland 1.00% 1.09% 1.44% 1.19% 0.72% 1.36%
Portugal 1.65% 1.8% 2.40% 1.52% 1.34% 1.14%
Italy 1.45% 1.44% 0.65% 1.03% 1.07%
Largely the same picture as ever, with the US leading the way, the UK in second and then a sliding scale of Europeans countries. Slovenia continues to pick its way up the pile for obvious reasons!
World Map to demonstrate

2. What's your age?

u17 17-19 20-25 26-30 31-35 36-40 41-50 51+ Total
2015 2.22% 12.04% 41.51% 24.66% 10.68% 4.87% 2.94% 1.08% 1395
2016 1.5% 8.9% 40.8% 24% 12% 5.4% 5.2% 2% 887
2018 Mar 1% 7.1% 33.5% 27.4% 16.2% 7% 5.7% 2.1% 617
2018 Aug 1.7% 9% 33.9% 26.4% 15.5% 7% 5% 1.5% 905
2019 1.5% 6.6% 33.2% 27.5% 16.4% 7.1% 5.8% 2% 972
2020 1.3% 6.8% 31.7% 28% 16.6% 7.2% 5% 2.5% 1420
Pretty much the same as last year, with the usual reddit demographics of majority 20 somethings dominating.

3. What's your gender?

'13 '14 '15 '16 '18 (1) '18 (2) '19 '20
Male 97.2% 97% 94.9% 93.4% 93.3% 93.6% 95.1% 94.9%
Female 2.8% 2.7% 4.8% 5.3% 5.3% 5.4% 3.7% 4.8%
Other - 0.33% 0.29% 0.78% 0.76% - -
Non-Binary - - - - 0.64% 0.99% 1.2% 0.4%
More normality here for reddit.

4. How much of the men's season do you watch/follow?

Type March '18 (%) August '18 (%) 2019 (%) 2020 (%)
Grand Tours 84.7 92.0 90.2 87.3
Monuments 79.1 74.9 79 75.9
WT Stage races 67.4 62.4 70.5 71.7
WT One day races 73.3 59.8 62.3 60.7
Non WT Stage races 32.6 16.7 17.4 25
Non WT One day races 34.8 13.7 17.4 20.7
Literally everything I can consume 35.9 18.1 21.1 27.1
Whilst GT following may be down (somehow), all the lower level stuff is up, which makes sense considering how desperate we have been for any racing during the season shutdown.

5. Do you maintain an interest in women's professional road racing?

Do you maintain an interest in women's professional road racing? '19 '20
Yes 49.8 49.2
No 50.2 50.8
Still very much a half/half interest in women's cycling on the subreddit.

6. How much of the women's season do you follow?

The following is true for the half of you that follows womens cycling.
How Much %
Just the biggest televised events 63.15%
Most of the live televised/delayed coverage stuff 29.08%
All televised racing 5.09%
Down to .Pro & beyond 2.69%

7. How long have you been watching cycling?

How Long %
Under a year 2,95%
1-3 years 19,50%
4-6 years 19,85%
7-9 years 14,10%
10-12 years 13,81%
13-15 years 7,15%
15-20 years 10,73%
20-25 years 6,17%
25 years + 5,75%
Simplified the years a little this time, but whilst we have a fair number of newbies, most people have picked the sport up since around 2013/14.

Sporting Favourites

8. Do you have like/dislike feelings about WT teams?

Once more, 14.4% of people really don't have feelings on the subject.
Of those that do:
AG2R Astana Bahrain Bora CCC Cofidis Quick-Step EF FDJ
Like 352 213 127 770 156 116 847 724 423
Meh 775 620 773 415 889 896 310 448 700
Dislike 52 356 263 31 112 141 71 37 53
Karma 300 -143 -70 739 44 -25 776 677 370
Israel Lotto Michelton Movistar NTT Ineos Jumbo Sunweb Trek UAE
Like 135 364 517 231 101 304 925 279 383 118
Meh 740 764 626 646 931 414 282 805 765 734
Dislike 302 40 52 326 121 562 53 97 42 331
Karma -167 324 465 -95 -20 -258 872 182 341 -213
So, the most popular team this year is Jumbo-Visma, followed by Quick-Step & Bora-hansgrohe. Least popular are Ineos & UAE.
As per usual, no one cares about NTT & CCC, with nearly 81% of users rating NTT as meh. Pretty damning stuff.
Lastly, we have the usual historical comparison of how teams have fared over time, normalised to respondents to that question on the survey.
Things to note then, firstly that the Astana redemption arc is over, seeing them back in the negative, maybe Fulgsangs spring issues helped aid that? The petrodollar teams of UAE & Bahrain are stubbornly negative too, with Israel keeping up the Katusha negative streak. Meanwhile, at the top end, EF & Jumbo go from strength to strength, whilst some others like Sunweb are sliding over time - their transfer policies no doubt helping that.

10. Do you ride a bike regularly?

Answer 2018Mar 2018Aug 2019 2020
For fun 61.5% 63.4% 59.9% 62.9%
For fitness 59.3% 59.6% 54.8% 59.8%
For commuting 46% 46% 45.6% 40%
For racing 20.6% 20.6% 15.9% 17.7%
No, I don't 14.2% 12.9% 14.8% 13.6%
Still a fairly small group of racers out of all of us

11. Out of the sports you practice, is cycling your favourite?

Yes No
58,29% 41,71%
A new addition to the survey prompted by a good point last time, just over half of us rate cycling as the favourite sport we actually do.

12. What other sports do you follow?

Sport #
Association Football / Soccer 50.78%
Formula 1 35.81%
American Football 26.27%
Basketball 22.46%
Track & Field 17.58%
Esports (yes, this includes DotA) 17.30%
Rugby 14.27%
Skiing 14.12%
Ice Hockey 13.63%
Baseball 12.15%
Motorsports (Not including F1) 10.59%
Cricket 10.52%
Tennis 9.53%
Chess 8.97%
Triathlon 8.69%
Biathlon 8.12%
Snooker 7.06%
Golf 6.92%
Swimming 6.85%
Ski Jumping 6.78%
Climbing 5.72%
Martial Arts 5.65%
Handball 5.44%
Darts 5.01%
Speed Skating 5.01%
Football always tops the charts, and Formula 1 continues to rank extremely highly among our userbase. Those who have a little following below 5% include Sailing, Fencing, Surfing, Boxing & Ultra-Running.
Other cycling disciplines
Sport #
Cyclocross 22.10%
Track Cycling 14.34%
MTB 8.97%
BMX 1.20%

13. Out of the sports you follow, is cycling your favourite sport?

Yes No
61.79% 38,21%
Good. Makes sense if you hang out here.

Subreddit stats

14. How often do you participate in a /Peloton Race Thread whilst watching a race?

2015 2016 2018Mar 2018Aug 2019 2020
I always participate in Race Threads during races 2.8% 2% 2.2% 4% 2.5% 3%
I follow Race Threads during races 41.7% 36.7% 38.1% 42.1% 42.5% 38.9%
I often participate in Race Threads during races 16.8% 19% 16.5% 18.9% 15.2% 13%
I rarely/never participate in Race Threads during races 38.7% 41.3% 43.1% 35% 39.8% 45.1%
Slightly less invested than before, reverting back to an older trade.

15. How do you watch Races?

Method 2018Mar 2018Aug 2019 2020
Pirate Streams 62% 46.5% 50.2% 47.9%
Free Local TV 55.7% 64.5% 59.6% 53.9%
Desperately scrabbling for Youtube highlights 37.9% 30.2% 28.2% 24.9%
Paid Streaming services 32.3% 35.4% 38.3% 46.3%
Year on year, paid streaming services go up - the increasing availability of live content legally continues to improve, and so do the numbers on the survey.

16. Where else do you follow races live (in addition to watching them)?

Type 2018Mar 2018Aug 2019 2020
/Peloton race threads 86.2% 83.4% 80.2% 76.9%
Twitter 30.5% 34.7% 33.3% 38.3%
PCS Liveticker - - 30.2% 32%
Official tracker (if available) 24%
The Cyclingnews liveticker 26% 23.5% 21.5% 18.9%
Sporza (site/ticker) 1.89% 9.5% 10.8% 10.8%
NOS Liveblog - 6.8% 7% 9.2%
Steephill 0.52% 13.5% 10.2% 8.2%
/Peloton discord 6.5% 5.4% 7.5% 7.2%
Other cycling forums 15.1% 8.1% 7.6% 7%
feltet.dk - 2.2% 5.4% 5.2%
Facebook 3.8% 5.4% 4% 4.2%
BBC Ticker - 3.5% 2.1% 4.1%
DirectVelo - 1.3% 1.6% 1.8%
Non Cycling Forums - 1.3% 1.2% 1.2%
/cyc/ - 1.3% 1% 0.6%
/peloton IRC ~0 0.8% 0.4% 0.5%
The PCS liveticker continues to have a strong following, whilst the cyclingnews ticker slowly slides into less usage over time.

17. Do you use /Peloton mostly in classic reddit or redesign when on the desktop?

Type 2018 Aug 2019 2020
Classic 75.1% 67.2% 46.2%
Redesign 24.9% 32.8% 53.8%
Time to abandon ship. The end has come.

18. With what version of reddit do you browse the sub?

Version 2019 2020
Official App 17.9 31.1
Desktop Classic 37.8 25.8
3rd Party App 18.3 17.2
Mobile Web 12.4 14.7
Desktop Redesign 13.7 11.2
Phone browsing is very much in vogue.

19. How did you find the sub?

How %
Through other forms of reddit, f.e. /bicycling 48.33%
Too long - can't remember 38.65%
Google search 9,11%
My friend told me 2,28%
I wanted to talk about my exercise bike 0.78%
Twitter 0.5%
Lantern Rouge Youtube 0.28%

Other bits and bobs

20. Did you think back in March we would see any more racing this year?

Yes No
52,81% 47,19%
Despite the threat, we have seen racing again

21. Will we manage to fulfill the rest of the UCI calendar without further Covid-19 issues postponing more races?

Yes No
25.3% 74.7%
Sorry to you 25%, Amstel, Roubaix & a bunch of other races have falled foul of COVID-19 related cancellations.

22. When did you become aware of Alexander Foliforov?

When %
Before the 2016 Giro 3,25%
22nd May, 2016 15,55%
On /pelotonmemes in 2020 21,13%
Who? 60,07%
If you didn't know of the man, watching him demolish the Giro field in 2016 on the stage 15 ITT should help to gain understanding

23. Who will win the 2020 Tour de France?

Rider %
Roglic 52,12%
Bernal 16,57%
Pinot 9,24%
Dumoulin 7,9%
N.Quintana 2,82%
Pogacar 1,41%
Richie Porte 0,35%
We can safely say that most of us were wrong about this one.
That's not a lot of confidence in Richie Porte either, the man who was to finish on the third spot of the podium. Alexander Foliforov (0,23%) had just a tiny number of votes less, and that man wasn't even in the race.

24. What for you was the defining cycling moment of the previous decade?

We had a lot of brilliant suggestions, but these were the clear five favourites when we tabulated the results.
Honorable mentions go to the Giro 2018, which had Tom Dumoulin winning, and of almost identical fascination to many of you - Tom Dumoulin going on someones porta-potty in the middle of the stage.
Little bit of recency bias perhaps, but that's better than ignoring that this was for the last decade and firmly insisting Tom Boonens 2005 WC win was the biggest thing. Special shoutout to almost all the Danes present in /peloton who voted for Mads Pedersens WC win last year. It's an understandable reaction.

25. Any suggestions for the Survey?

New Questions
We promise to feature one of these suggestions in the next survey
Suggestions
We will try to implement this. But it will also skew results.
About the Survey
The subscribers are torn on Women's cycling, nearly a 50/50 split there as the survey showed - The moderators at /peloton are firmly in the "more cycling is better" basket, and we will continue to get as good coverage of womens cycling as possible.
Are you trying to give the moderators PTSD? Because this is how you give the moderators PTSD.

26. Any suggestions for the sub?

ALSJFLKAJSLDKJAØLSJKD:M:CSAM)=#/()=#=/")¤=/)! - Your moderator seems to be out of function. Please stand by while we find you a new moderator
The Weekly threads are great for these types of questions, where several people can contribute and build up once it is understood which information is relevant.
Our experience is that "limited" will never be so, if we're going to moderate it fairly. Moderating is not a popularity contest, but believe it or not, we're actually trying to be as fair as possible. and for that, we need rules that are not subjective. Unless you have a stationary exercise bike.
All of these are good suggestions, but remember that all of you can also contribute - The mods are sometimes stretched thin, specially in the middle of hectic race schedules. It's easier if one of you has a way to contact a rider or a person of interest and can facilitate the initial communication.
We've worked on this! The Official Standard is now as follows: [Race Thread] 202x Race Name – Stage X (Class)
This sounds as a nice community project for the after-season, and hopefully many of you subscribers can contribute.
Come with suggestions on how to tidy it up!
We have chastised all the mods. They are now perfectly trained in gender-neutral pronouns. Be well, fellow being.
If we can implement this for hard liquor, you know we will.
The spoiler rule is one that is discussed frequently - in general - some users absolutely hate it, but a majority love it. Perhaps we'll include a question in the next survey to see how this divide is exactly.
We actually do - whenever there is a matter of life or death, we think public information is more important than a spoiler rule. But at the same time, we try to collect all the different posts into one main thread, so to keep things focused and letting very speculative posts meet with hard evidence from other sources.
This is a tough ask of the internet. While we can agree that voting should be done accordingly to what insights they bring, not subjective opinions, it is very hard to turn that type of thinking around. We can ask of you, our subscribers, that you please think twice about hitting that downvote button, and only do so because of you think a post is factually incorrect, not because it differs with your own subjective opinion.
That's the primary analysis of the survey! Feel free to contribute with how you experience things here!
submitted by PelotonMod to peloton [link] [comments]

How to Safely Flash Official One UI 2.5 (DBT) on SM-N960F

Hey Guys!
https://youtu.be/hzHzSk5KPUE
I will be showing you how to flash Official One UI 2.5 Germany DBT ROM on your device without deleting any data (if OEM is enabled otherwise you will have to backup).
3 Main Requirements before you start.
  1. Make sure your chipset is Exynos (you can find out using CPU-Z app).
  2. Model number must be either SM-N960F or SM-N960F/DS.
  3. Binary Version should be either 6 or lower. (see the video below for better understanding)
1.1. On Phone > Goto Settings > Scroll Down > About Device > Software Information > Tap Build number 7 times > Go back to settings main page > scroll down > you will find new option called Developer options. Click on it > You will than find OEM unlocking (if OEM unlocking is not visible or is already enabled than you can skip to section *1.2*. If OEM unlocking is disabled, make sure you backup your device using SmartSwitch.
1.2. Download the necessary files from the video description. (Odin, Stock ROM (DBT), SmartSwitch, Samsung USB Drivers).
1.3. If you have SmartSwitch and USB Drivers already skip to *1.4*, disconnect cable to your device if connected than once you have installed both software/drivers make sure you reboot your PC. Launch SmartSwitch and simply press backup.
1.5. Once you are done now run Odin as administrator, click BL, AP, CP and CSC one by one and click on file that matches the starting letters located in your stock rom folder. NOTE: You will have 2 CSC files, Home_CSC is to keep data and not to format, CSC is to format the device. Pick the one you desire.
1.6. On your device, power it off, than plug in a usb cable to your PC, hold volume down + bixby button and power button simultaneously once it vibrates leave the power button but keep holding volume down + bixby button until you see warning screen, press volume up once to enter download mode.
1.7. Now you should see a blue highlighted ID:COM on Odin, you can simply press Start and it will do its job.
1.8. After it shows the PASS sign, you may close the odin and enjoy the One UI 2.5! :) If you get to know that your region released the One UI 2.5 you can follow the same step and flash your region rom and you will get the OTA updates with no issues.
I also made a video since there isn't a video that explains step by step, I hope you enjoyed and thanks!
submitted by technogenuine to GalaxyNote9 [link] [comments]

Virtual Reality: Where it is and where it's going

VR is not what a lot of people think it is. It's not comparable to racing wheels, Kinect, or 3DTVs. It offers a shift that the game industry hasn't had before; a first of it's kind. I'm going to outline what VR is like today in despite of the many misconceptions around it and what it will be like as it grows. What people find to be insurmountable problems are often solvable.
What is VR in 2020?
Something far more versatile and far-reaching than people comprehend. All game genres and camera perspectives work, so you're still able to access the types of games you've always enjoyed. It is often thought that VR is a 1st person medium and that's all it can do, but 3rd person and top-down VR games are a thing and in various cases are highly praised. Astro Bot, a 3rd person platformer, was the highest rated VR game before Half-Life: Alyx.
Lets crush some misconceptions of 2020 VR:
So what are the problems with VR in 2020?
Despite these downsides, VR still offers something truly special. What it enables is not just a more immersive way to game, but new ways to feel, to experience stories, to cooperate or fight against other players, and a plethora of new ways to interact which is the beating heart of gaming as a medium.
To give some examples, Boneworks is a game that has experimental full body physics and the amount of extra agency it provides is staggering. When you can actually manipulate physics on a level this intimately where you are able to directly control and manipulate things in a way that traditional gaming simply can't allow, it opens up a whole new avenue of gameplay and game design.
Things aren't based on a series of state machines anymore. "Is the player pressing the action button to climb this ladder or not?" "Is the player pressing the aim button to aim down the sights or not?"
These aren't binary choices in VR. Everything is freeform and you can basically be in any number of states at a given time. Instead of climbing a ladder with an animation lock, you can grab on with one hand while aiming with the other, or if it's physically modelled, you could find a way to pick it up and plant it on a pipe sticking out of the ground to make your own makeshift trap where you spin it around as it pivots on top of the pipe, knocking anything away that comes close by. That's the power of physics in VR. You do things you think of in the same vain as reality instead of thinking inside the set limitations of the designers. Even MGSV has it's limitations with the freedom it provides, but that expands exponentially with 6DoF VR input and physics.
I talked about how VR could make you feel things. A character or person that gets close to you in VR is going to invade your literal personal space. Heights are possibly going to start feeling like you are biologically in danger. The idea of tight spaces in say, a horror game, can cause claustrophobia. The way you move or interact with things can give off subtle almost phantom-limb like feelings because of the overwhelming visual and audio stimulation that enables you to do things that you haven't experienced with your real body; an example being floating around in zero gravity in Lone Echo.
So it's not without it's share of problems, but it's an incredibly versatile gaming technology in 2020. It's also worth noting just how important it is as a non-gaming device as well, because there simply isn't a more suitably combative device against a world-wide pandemic than VR. Simply put, it's one of the most important devices you can get right now for that reason alone as you can socially connect with no distancing with face to face communication, travel and attend all sorts of events, and simply manage your mental and physical health in ways that the average person wishes so badly for right now.
Where VR is (probably) going to be in 5 years
You can expect a lot. A seismic shift that will make the VR of today feel like something very different. This is because the underlying technology is being reinvented with entirely custom tech that no longer relies on cell phone panels and lenses that have existed for decades.
That's enough to solve almost all the issues of the technology and make it a buy-in for the average gamer. In 5 years, we should really start to see the blending of reality and virtual reality and how close the two can feel
Where VR is (probably) going to be in 10 years
In short, as good as if not better than the base technology of Ready Player One which consists of a visor and gloves. Interestingly, RPO missed out on the merging of VR and AR which will play an important part of the future of HMDs as they will become more versatile, easier to multi-task with, and more engrained into daily life where physical isolation is only a user choice. Useful treadmills and/or treadmill shoes as well as haptic suits will likely become (and stay) enthusiast items that are incredible in their own right but due to the commitment, aren't applicable to the average person - in a way, just like RPO.
At this stage, VR is mainstream with loads of AAA content coming out yearly and providing gaming experiences that are incomprehensible to most people today.
Overall, the future of VR couldn't be brighter. It's absolutely here to stay, it's more incredible than people realize today, and it's only going to get exponentially better and more convenient in ways that people can't imagine.
submitted by DarthBuzzard to truegaming [link] [comments]

[SA] My experience with getting a name and gender change in Adelaide

If you haven't seen my first post about getting a diagnosis and HRT, you can find it here.
Hey, I'm Emma (legally now!!!), a 29 year old trans woman, and as of today I've completed almost everything involved in the name and gender change process. Given it's a ton of work (and a fair expense), I thought I'd write up the steps I followed to make it easier for anyone else trying to do the same thing.

Prepare

Get a notebook or a text doc on your computer, or something like that. Write down every company you interact with, everyone who emails you, every place you have an account with, basically anything that has your deadname on it.
Now, go through these and see how many you can just change without providing proof. A lot of companies just let you edit it (or will do so if you email them and ask). For the ones that don't, start noting down what ID they require. A lot will just be happy with a scan of your birth certificate, but some will want photo ID, a utility bill, or a certified copy of one of those.
Certified copies are a bit of a pain, basically you need to make a photocopy (or scan and print) the document, then take the copy and original to someone "authorised" who will look over the two, then stamp and sign it to say they're identical. Companies vary on who they'll allow to certify a document, but basically everyone accepts a Justice of the Peace (JP), and most councils run a free JP service, which is what I used. Note that JPs can certify email bills, but in a slightly different way - they basically just get you to swear that it's a legitimate copy and sign some stuff, but as far as I can tell it works just fine.

Get a letter from a medical professional or psych

In South Australia you *do not* need to have had surgery to qualify for a gender change. I got mine on the back of ~4 months HRT, and I believe psychiatric help will also do. I asked my endocrinologist for a letter and she was happy to provide one.

The Birth Certificate

Okay, here's the big one! You'll need to fill out a Change of Sex or Gender Identity form (PDF, Website) and a Change of Name form (PDF, Website). Read the hell out of the websites and PDFs, they're long and confusing but you need to know this stuff! Print out the forms and fill them out. On the gender change form, you can choose from Male, Female, Non-binary, or Indeterminate/intersex/unspecifed.
The cost if you do both at once is $321 (at time of writing). I got a bit worried by the combined discount because the forms both have individual payment sections, but what you do is just put the $321 on one form and write "see [first form's name] for full amount" on the other and they figure it out. This fee includes them sending you two (!!) nice new birth certificates. Both are just normal looking certificates, but one only has your new name and gender on it, and the other has a change list on the back, which includes your old ones (this is very useful for changing your name elsewhere).
Another tip for the forms is that there's basically only one spot on the name form that asks for your new name, every other field wants your deadname. On the gender change form, it doesn't ask for your new name at all, they just figure it out because you're sending the forms in at the same time. If you have any questions about the form you can call the office of Consumer and Business Services on 131 882. The person I spoke to was really friendly and helpful, and got the answers I needed after a bit of searching.
You're going to need a bunch of ID for these forms, and you'll also need a witness for the change of name, so it's time to head to a JP (again, use the free council service) and get that done. I was told by CBS that each form needed its own ID (so two copies of each document), so make sure you've got enough copies. I also recommend making a backup copy of your old birth certificate, because you're putting the original in an envelope and posting it off, and that's kinda dicey imo. I also really recommend using some combination of registered post/tracking/insurance, depending on your level of worry.
Post the forms off along with your old birth certificate and ID, and wait anxiously. The CBS website estimates about a month's wait, but mine got done in about 10 days! You don't get any warning that it's done, just a letter from the SA Gov in the mail with the new birth certs in it. Take a moment to celebrate this, because for me opening that letter was the best feeling in the world. You earned it, well done!

Medicare

I'm going to tell you right now: do not bother trying to look up the process for this. It's the classic bureaucracy experience. Instead, just email [[email protected]](mailto:[email protected]) with the subject line Change of Name (DeadSurname DeadFirstname) and a scan of the front and back of your new birth certificate that shows the changes. No other stuff, no forms (this is important), just that. They send you an autoreply that says it'll take months, but that's for new applications and stuff like that. I got a response in 9 days - a lady calling from a blocked caller ID (thanks Services Australia) to confirm a couple of details, and the change went through that afternoon. Obviously it takes a while to send out the new card, but in the meantime if your Medicare is linked to MyGov, you can download the Medicare app (confusingly called Express Plus Medicare on iOS) and it has a card display feature that people should accept. There's no charge for this process.
Note that you may need to get prescriptions/blood test forms/etc re-issued in your new name, I'm not sure about this but I'm emailing my endo tonight.

Photo ID

I don't have a driver's license, so I can't comment on that, but here's the Proof of Age Card process, which I imagine is fairly similar? First, you'll need to fill out an application form (PDF, Website), then head into Services SA (don't do the online application, I'm guessing you'll want a new photo), and let them know you've changed your name and want to update your proof of age card. They'll give you a form to fill out that updates your details with the government department, and ask to see your birth certificate (bring the original with the change list). Fill out the form and take that, your birth cert, your old proof of age card, and your application form from earlier to the counter when you get called, they'll process it, take your photo, and a week or two later you should have your new card! The cost is $25. Here's me celebrating about it!

ATO

Second easiest of the lot! You just go to their website via MyGov, choose the option from the menus, enter in your details exactly as they appear on your birth cert (pay attention to the little diagram, it explains where to find everything), it does some verification magic, and you're done! No wait, no documents, no forms!

SA Water

The best one. Just log in to their website, hit My Settings, then Edit Details. Done!

Everything Else

I highly recommend getting some easy utilities done first - a lot of other places require a utility bill in your new name, and you'll be waiting for your next billing date for them. Once you have them and your list of what needs certified copies, head back to the JP and get them all done in a big batch. You'll probably need a lot of copies of your birth cert (front and back to show the change) as well. Head to the post office and buy some prepaid envelopes too.
Company website searches can suck, I recommend googling [company name] change name. You'll usually find a PDF form with all the requirements or a web page that spells it out. Worst case, give them a ring and they can help you out. Also, if you have a will, don't forget to update that too!
AGL: You need to call them. They may also need to re-create your online account to make it show the new name in there.
NAB: Need to go in person to a branch with your birth cert (showing the change) AND photo ID in your new name. This is a recent policy change.
ING: You need to fill out a form, provide certified copy of your birth cert (front and back) and post it all to them. Took about a week for them to call me to verbally confirm the change. They posted the cards out the same day, and provided SMS updates as well.
Super: Each fund should have the details on their website, the two I dealt with required a posted form and certified ID.
Amex: You call them, upload a scan of your birth cert (front and back) through the website while on the phone, and they sort it out.
Optus: Posted form, birth certificate showing change (front and back). They don't say it needs to be certified but I did it anyway to be safe. The address listed on the form and the website are different. I tried the form's address and it worked fine, took 9 days.
Council: I called them to ask, just needed to email them scans of my birth certificate (front and back), might vary from place to place
House title, etc: Have not tried. Expensive and needs a conveyancer.
submitted by emmadaboutlife to transgenderau [link] [comments]

How to generate (relative) secure paper wallets and spend them (Newbies)

How to generate (relative) secure paper walletsEveryone is invited to suggest improvements, make it easier, more robust, provide alternativers, comment on what they like or not, and also critizice it.
Also, this is a disclaimer: I'm new to all of this. First, I didn't buy a hardware wallet because they are not produce in my country and I couldnt' trust they are not tampered. So the other way was to generate it myself. (Not your keys not your money) I've instructed myself several weeks reading various ways of generating wallets (including Glacier). As of now, I think this is THE BEST METHOD for a non-technical person which is high security and low cost and not that much lenghty.
FAQs:Why I didn't use Coleman's BIP 39 mnemonic method? Basically, I dont know how to audit the code. As a downside, we will have to really write down accurately our keys having in mind that a mistype is fatal. Also, we should keep in mind that destruction of the key is fatal as well. The user has to secure the key from losing the keys, theft and destruction.
Lets start
You'll need:
Notes: We will be following https://www.swansontec.com/bitcoin-dice.html guidelines. We will be creating our own random key instead of downloading BitAddress javascript for safety reasons. Following this guideline lets you audit the code that will create the public address and bitcoin address. Its simple, short and you can always test the code by inputting a known private keys to tell if the bitcoin address generated is legit or not. This process is done offline, so your private key never touches the internet.
Steps
1. Download the bitcoin-bash-tools and dice2key scripts from Github, latest Ubuntu distribution, and LiLi, A software to install Ubuntu on our flash drive (easier than what is proposed on Swansontec)

2. Install the live environment in a CD or USB, and paste the tools we are going to use inside of it (they are going to be located in file://cdrom)

  • Open up LiLi and insert your flash drive.

  • Make sure you’ve selected the correct drive (click refresh if drive isn’t showing).
  • Choose “ISO/IMG/ZIP” and select the Ubuntu ISO file you’ve downloaded in the previous step.
  • Make sure only “Format the key in FAT32” is selected.
  • Click the lightning bolt to start the format and installation process
  • [https://99bitcoins.com/bitcoin-wallet/pape\](https://99bitcoins.com/bitcoin-wallet/pape)

    3. Open the Ubuntu environment in a offline computer that will never touch the internet again (there is some malware that infect the BIOS so doing it in your regular computer is not safe to my understanding)

    Restart your computer. Clicking F12 or F1 during the boot-up process will allow you to choose to run your operating system from your flash drive or CD. After the Ubuntu operating system loads you will choose the “try Ubuntu” option.
    4. Roll the dice 100 times and convert into a 32-byte hexadecimal number by using dice2key

    To generate a Bitcoin private key using normal, run the following command to convert the dice rolls into a 32-byte hexadecimal number:source dice2key (100 six-sided dice rolls)

    5. Run newBitcoinKey 0x + your private key and it will give you your: public address, bitcoin address and WIF.Save the Private Key and Bitcoin Address. Check several times that you handwritten it correctly. You can check by re entering the code in the console from your paper. (I recommend writing down the Private Key which is in HEX and not the WIF since this one is key sensitive and you can lose it, or write it wrong. Also, out of the private key you can get the WIF which will let you transfer your funds). If you lose your key, you lose your funds. Be careful.
    If auditing the code for this is not enough for you, you can also test the code by inputting a known private keys to tell if the bitcoin address generated is legit or not.
    I recommend you generate several keys and addresses as this process is not super easy to do. Remember that you should never reuse your paper wallets (meaning that you should empty all of the funds from this one adress if you are making a payment). As such, a couple of addresses come handy.
    At this point, there should be no way for information to leak out of the live CD environment. The live CD doesn't store anything on the hard disk, and there is no network connection. Everything that happens from now on will be lost when the computer is rebooted.
    Now, start the "Terminal" program, and type the following command:
    source ~/bitcoin.shThis will load the address-calculation script. Now, use the script to find the Bitcoin address for your private key:
    newBitcoinKey 0x(your dice digits)Replace the part that says "(your dice digits)" with 64 digits found by rolling your pair of hexadecimal dice 32 times. Be sure there is no space between the "0x" and your digits. When all is said and done, your terminal window should look like this:
    [email protected]:~$ source ~/[email protected]:~$ newBitcoinKey 0x8010b1bb119ad37d4b65a1022a314897b1b3614b345974332cb1b9582cf03536---secret exponent: 0x8010B1BB119AD37D4B65A1022A314897B1B3614B345974332CB1B9582CF03536public key: X: 09BA8621AEFD3B6BA4CA6D11A4746E8DF8D35D9B51B383338F627BA7FC732731 Y: 8C3A6EC6ACD33C36328B8FB4349B31671BCD3A192316EA4F6236EE1AE4A7D8C9compressed: WIF: L1WepftUBemj6H4XQovkiW1ARVjxMqaw4oj2kmkYqdG1xTnBcHfC bitcoin address: 1HV3WWx56qD6U5yWYZoLc7WbJPV3zAL6Hiuncompressed: WIF: 5JngqQmHagNTknnCshzVUysLMWAjT23FWs1TgNU5wyFH5SB3hrP bitcoin address: [email protected]:~$The script produces two public addresses from the same private key. The "compressed" address format produces smaller transaction sizes (which means lower transaction fees), but it's newer and not as well-supported as the original "uncompressed" format. Choose which format you like, and write down the "WIF" and "bitcoin address" on a piece of paper. The "WIF" is just the private key, converted to a slightly shorter format that Bitcoin wallet apps prefer.
    Double-check your paper, and reboot your computer. Aside from the copy on the piece of paper, the reboot should destroy all traces of the private key. Since the paper now holds the only copy of the private key, do not lose it, or you will lose the ability to spend any funds sent to the address!
    Conclusion
    With this method you are creating an airgapped environment that will never touch the internet. Also, we are checking that the code we use its not tampered. If this is followed strictly I see virtually no chances of your keys being hacked.
    How to spend your funds from a securely generated paper wallet.
    Almost all tutorials seen online, will let you import or sweep you private keys into the desktop wallet or mobile wallet which are hot wallets. In the meantime, you are exposed and all of your work to secure the cold storage is being thrown away. This method will let you sign the transaction offline (you will not expose your private key in an online system).
    You'll need:
    The source of this method is taken from CryptoGuide from Youtube https://www.youtube.com/watch?v=-9kf9LMnJpI&t=86s . Basically you can follow his video as it is foolproof. Please check that Electrum distribution is signed.
    The summarized steps are:
    Download Electrum on both devices and check its signed for safey.Disconnect your phone from the internet (flight mode= All connections off) and input your private key in ElectrumGenerate the transaction in your desktop and export it via QR (never leave unspent BTC or you will lose them)In your phone, open Electrum > Send > QR (this will import the transaction) and scan the desktop exported transactionSign the transaction in your phone.Export the signed transaction in QRLoad the signed transaction in the desktop Electrum and broadcast it to the network.Wait until 3 confirmations to connect your phone to the internet again.
    Ideas for improvement:
    So thats it. I hope someone can find this helpful or help in creating a better method. If you like, you can donate at 1Che7FG93vDsbes6NPBhYuz29wQoW7qFUH
    submitted by Heron-Express to Bitcoin [link] [comments]

    Star Trek games you can get right now

    Hi everyone, my last post about wanting to see more star trek games got a lot of comments (if not a lot of Karma) and so I thought you might be interested in what Star Trek games are around right now.
    Edit: Please feel free to add your own, or add links to games with mods (though please include the link to the mod as well if you can) that convert them into Star Trek games! I only limited this to official star trek games in the hopes that maybe people might buy them, and thus produce sales data that might make CBS see that there's a good monetary incentive to make more games available.
    First off, the original Starfleet Command is a great game that still holds up, even if it's graphics look like they're rendered in cardboard. You can install it, go to skirmish, and make yourself a 9 on 9 fleet battle between any of the TOS factions they included. I just went three rounds in a half hour and it's honestly probably, pound for pound, the best currently downloadable Star Trek game available. Go watch the Battle of the Binary Stars and set yourself up a round, it's real fun I promise!
    https://www.gog.com/game/star_trek_starfleet_command_gold_edition
    Next up, Star Trek Bridge Crew. Looks really cool and fun, but I lack a VR headset and playing without one was, for me at least, basically impossible. I imagine it's better with friends and with the appropriate equipment, but unless you've already got those it's kind of hard to justify buying it.
    https://store.steampowered.com/bundle/7939/Star_Trek_Bridge_Crew__Bundle_Game_and_The_Next_Generation/
    Star Trek Online has been around for a while, and you likely already know it. It's an MMO on the decline and I haven't personally played the expansions, but there is plenty of trek themed content around a serviceable MMO that once upon a time admirably carried the burden of being our only way to play past the end of Voyager in the prime timeline. And hey, some of the stories are cool! (It's great for people who love buying lootboxes!)
    https://store.steampowered.com/app/9900/Star_Trek_Online/
    Star Trek Starfleet Academy is a flight sim that has footage of the original trek actors, and is well reviewed, though I couldn't tell you how it is personally. Might pick it up on sale, but if I'm being honest, probably not.
    https://store.steampowered.com/app/364810/Star_Trek_Starfleet_Academy/
    I don't really count Star Trek Timelines, because it's basically a fancy UI over a random number generator phone game, but it exists, technically, so here.https://store.steampowered.com/app/600750/Star_Trek_Timelines/
    Also, for the sake of completeness, there are some adventure games (that seem neat but I'm not buying for $10 a pop)
    https://store.steampowered.com/app/364800/Star_Trek_Judgment_Rites/
    https://store.steampowered.com/app/359650/Star_Trek__25th_Anniversary/
    And, unless you wanna go trolling around for an old physical copy of Elite Force or The Fallen somewhere, that's it!
    ...
    ...
    Unless of course you consider piracy as an option to get games no longer being sold, in which ca-*transmission lost*
    submitted by Wareve to startrek [link] [comments]

    HIRE A HACKER: SOLIDARITY HACKER FOR HIRE REVIEWS

    BEST HACKER FOR HIRE TO HACK A CELL PHONE Hire a hacker that needs not to jailbreak your phone in order to use these iOS hacking apps. Once you do that, the option to get the seniorhackers app/service often comes up with an address for you to contact for further directives. The ethical hacking services can be used to analyze keychain contents, including passwords, keys, certificates and messages etc. for any sensitive information.
    Speaking in developer language, seniorhacker.tech offers binary analysis using o tool, keychain analysis using keychain_dumper, working, Binary decryption using dump decrypted and database reading using SQLite. Besides these functions, the hacking tool also lets you create, edit and install the tweaks.
    The iOS hacking app was developed by senior hackers for an easy to use web GUI and can be used in various programming functions such as Cycript integration, class dumps, automatic jailbreak-detection bypasses, automatic SSL certificate pinning bypasses, re-implemented objc_msgSend for logging and tracing function calls in real-time.
    SOLIDARITY HACKER REVIEWS — Best iOS / MOBILE PHONE Hacking Application For iOS Myriam iOS Security App was developed by security researcher and GitHub user Solidarityhacker who created a learning platform for hack techies to become the next big iOS hackers where people can Hire a Hacker. As a result, this iOS hacking tool is the perfect place to start for any newbie iOS hacker to develop their skills.
    Some of the hacking challenges a.k.a. device vulnerabilities that newbie hackers can exploit with this mobile hacking application include Authentication, In-App Data modification, App Activation Bypass, Jailbreak Detection, In-App Resources, and variable Modification.
    To Provide a powerful tool that makes use of the widely-used Nmap scanner in the background to map and scan the connected networks. Once you install the Network Mapper app from Play Store, it will automatically download and install the required Nmap binaries from the Internet and provide you with an easy-to-use GUI to perform scans. Using Network Mapper, you can do a comprehensive scan on the network to identify live hosts and gather a range of information like open ports, network attributes, OS information, etc.
    Trustworthy Certified Ethical Hackers For Hire
    Solidarityhacker.com/services/ Hackers For Hire committed to excellence. There are situations when you just think how to hire a hacker, but you just hesitate to contact a hacker. Feel free to get in touch with us and maybe we might offer you the exact hire a hacker service you are looking for.
    Here are a few of most widely used hacker for hire services.

    Hire a Hacker Today! Your identity will be kept anonymous, Send a message to [email protected]
    submitted by jhondaski5444 to u/jhondaski5444 [link] [comments]

    Day 6: The Tools You Think You Need, and Altar Talk

    Originally I looked up a few big ol' lists of "essentials" for witches. I looked at lists of altar necessities and Wicca specific tools, and you get the idea... it was a lot. Mostly it was a lot of "dicks and wombs," but we'll get to that.
    I had originally planned to go through a list of tools one by one and talk about correspondences and substitutes, but the more I went down that road, the more WRONG it felt. When I first started this project, I asked a group of experienced witches what they wish they had known when they first started and what they'd like new witches to know. About 150 witches responded and there were 2 things that came up more than anything else:
    1. You don't need to buy ANYTHING
    2. Your path is YOURS
    The third thing was to protect yourself from scammers and predatory people, and we already covered that.
    I will have entire days dedicated to certain tools and practices later in the month. This is just the briefest overview of some tools and altars.
    While you don't NEED to buy anything for your altar, and you don't NEED an altar at all, you might WANT to. If you look up the correspondences for most common altar items you will find a lot of things that are considered to be "masculine" or "feminine."
    Typically, feminine is associated with darkness, passiveness, quiet, home, and CONTAINERS. (Circles and triangles often represent containers. Containers = womb.)
    Typically, masculine is associated with light, activity, exploration, and pointy things. (Because pointy = penis.)
    Just remember that you are allowed and encouraged to create your own associations. You do not have to subscribe to this binary. I reject it passionately, but I don't have a problem with anyone who enjoys it. There can be a sense of empowerment that comes from it. Your path is yours, and if it involves a bunch of dicks and wombs, I support your decision. I just don't want anyone stumbling into a bunch of dicks and wombs because they learned it was the "right way" to do things. (I'm officially done saying "dicks and wombs" now.)
    Even though you are the only tool you need, you may WANT some. In my opinion there are 3 main types of magical tools. Functional, mood setting, and religious. There are hybrids and exceptions and other ways to classify them, but that's how I'll be doing it here today. Also, I'm talking about non-consumable items that are meant to be reused often.
    Most functional tools (chalice, cauldron, mortar and pestle, boline) have very simple substitutes. (Chalice = cup, cauldron = cooking pot or bowl, mortar and pestle = spice or coffee grinder, boline = knife. A boline is a hybrid of religious and functional. If you follow the religion, you will probably want to follow the recommendations. However, since that religion is Wicca, it's usually okay if you don't/can't.)
    Tools that exist for purely magical reasons (like a wand, athame, and scrying tools) are completely unnecessary, but they can be helpful to get in the mood and they can also be a lot of fun if you love shopping or if you're the crafty type.
    I have made many wands, and I'm planning to make another one soon. One of the first, when I was probably 15 or 16, that I used for about 4 years and probably still have somewhere, is one that i made from a bone and a quartz point that fir perfectly into one of the joint ends. I used a leather cord around it and made a velvet lined box stuffed with herbs to store it in. Most recently, I used a bamboo toothpick. I may use the stem of white or purple sage to create a new wand soon. I have one of each on my wall right now and something about the fragility of them is really calling to me right now. Of course, the job of a wand is to point, and most of us do that pretty easily without a specialty tool.
    An athame is also a Wiccan tool, and purely religious. It is not used for physically cutting anything and often does the same job as a wand.
    Scrying tools may seem necessary, but these are also among the easiest to replace. My black mirror has never been a specialty made mirror. It does technically cost more, but that's because I use the easy to clean, shiny, deep black surface of my phone. There is literally nothing more connected to me. It holds all of my secrets and connects me to the world. With either the phone completely off or the screen off, it has always been useful to me. We will cover and try a few methods of scrying next week, so I will give you quite a few options then.
    Some things, like tarot cards, can't be replaced. If you want to do tarot readings, you need tarot cards. If you want to do card readings, you can use cards other than tarot. You can use oracle cards or a deck of playing cards (my favorite.) Honestly you can use anything, but these three options will give you a strong starting point without forcing you to create an entire system on your own.
    My general advice for tools is this- you don't need it. If you want it, buy it. If you want it and can't afford it right now- find a substitute. If you aren't sure if you want it- practice with a substitute first. Think about what it's for, what it means, and what it means to you, before you buy it. (If impulse buying benefits your life and doesn't harm your finances- go bananas! I'm not here to steal anyone's joy, just offering practical tips for the people who feel pressured into spending.)
    Your assignment is this: Look up a general list of tools and really think about the tools you want. (Remember that you don't need them and that it is perfectly okay to have things because you want them.) Make a note of the things you don't need and don't want,
    For today's part 2 we are going to talk about altars. I posted a picture of mine in here sometime recently, so you can see what my current setup looks like.
    There is no standard or correct altar. I'll probably repeat this on Day 8, but do be a little wary if you choose to post pictures of your altar. For some witches, this is akin to posting a picture of your driver's license. It can be an intensely personal space and there is an idea that someone can hex you using that information. I don't have a problem posting mine because a huge part of its function it to just be pretty and feel witchy. I do still cover, remove, or replace certain things when I take photos, so I do somewhat believe this idea. Also, make sure that you don't have any identifying information (like your actual drivers license) in the photo/s.
    If you want to know if it’s okay to have or not have something on your altar, the answer is yes. If you want to know if a certain size, shape, or orientation is okay for your altar, the answer is yes. Anyone who tells you you’re wrong will NEVER reach the levels you will, because they choose to sabotage themselves. They are restricting themselves. Even in deity work. While some people do choose to worship a deity and then start researching to find the deity that fits them, a lot people are called to serve or work with a particular deity. A LITERAL GOD who is calling you does not care what’s in your hand when you answer. They just don’t. The moon doesn’t care, the earth doesn’t care, your ancestors don't care, the fae don't care, nothing and no one that will lend you its energy gives a single fuck what you are pointing with. The energy responds to how you relate to energy.
    So your altar should include the things that help you do that. If that means a deck of cards and joint- great. If it means a glittering collections of crystals and candles set atop a gorgeous hand-painted tapestry- also great. If it means you put your tools in a box that you stash under your bed and you open it up for an instant altar- awesome. If it's a repurposed mint tin with a crystal, a candle, and a pinch of herbs- adorable.
    Again, if you follow a certain religion, you may want to follow the conventions of that religion.
    If what drew you to witchcraft was largely the aesthetic, make your space as beautiful as you want.
    If you really don't want an altar and you'd rather just store things in places where they won't turn into cat toys, be swallowed by toddlers, or collect dust- do it.
    If you want your altar to hold your tools nearby so you know where to find them- EXCELLENT.
    Are you noticing a trend?
    When I started out, my altar was on a nightstand in the north corner of my room with a black crushed panne velvet altar cloth, and dark EVERYTHING. I had pewter pendants, a black plastic chalice with dragons or something on it, I had pentagrams on things, I had my tarot cards in the dark green crushed panne velvet bag I made. I had my wand in it's box, and I had my Book of Shadows. I had incense. SO MUCH INCENSE. And herbs. So many herbs in baggies and bowls and just chilling out in my multiple mortars and pestles. I used to put offerings on my altar- something I don't think I even have room for now. I went through a long period with no altar at all, and a stint of an "altar in a box." If you look for the picture post, I describe my current setup there. My life and my values have changed. Sometimes I do miss the dark vibes and the heaviness of the smell of bags of powder incense and the wax drippings and the very "ready for ritual" feeling I got. Now I see my altar and I'm "ready for work." I don't
    Like everything else in magic, it will change with you. And like everything else, it should be in tune with your values. Tomorrow we will look into those, and try some automatic writing. Don't worry, it probably won't hurt....
    So tell me (if and as much as you are comfortable...)
    1. What tools are you giving yourself permission to not have? What are you giving yourself permission to buy (if/when you can?)
    2. Has your idea of your perfect altar changed at all?
    3. How is meditation going?
    Again, we'll revisit most of these things through the month, I just wanted to throw something a little lighter at you today and reinforce that you don't need to buy anything, before I start recommending a bunch of "things." See you tomorrow!



    All information presented is copyrighted material, you may not reproduce any part in any way except as permitted by US Copyright law. For info about reproduction permission, DM me.
    My current goal is to turn this into a book, and perhaps repeat this type of "course" in the future. I truly believe there is no cost of admission to witchcraft and I will never ask you to buy anything (from me or otherwise.)
    If you would like and are comfortably able to leave a tip, I do have CashApp, Venmo, and Paypal. (Starving artist is a lifestyle choice, but not-starving artist is great too. And no, I'm not actually starving, but I am looking at paying some money to get this project turned into a book and I've got my eye on this tarot deck...)
    submitted by Alarming-Biscotti to 30daywitch [link] [comments]

    Codemagic iOS build failed

    Hello everyone.
    does anyone have any idea what is the problem? unfortunately i'm not familiar with iOS compiling and as you can see i'm using codemagic to build for iOS but i have no idea what is this error all about
    ​ ``` Failed to build iOS app Error output from Xcode build: ↳ ** BUILD FAILED **
    Xcode's output: ↳ /Users/buildeprograms/flutte.pub-cache/hosted/pub.dartlang.org/permission_handler-5.0.1+1/ios/Classes/strategies/PhotoPermissionStrategy.m:39:13: warning: enumeration value 'PHAuthorizationStatusLimited' not handled in switch [-Wswitch] switch (authorizationStatus) { ^ /Users/buildeprograms/flutte.pub-cache/hosted/pub.dartlang.org/permission_handler-5.0.1+1/ios/Classes/strategies/PhotoPermissionStrategy.m:39:13: note: add missing switch cases switch (authorizationStatus) { ^ 1 warning generated. /Users/buildeprograms/flutte.pub-cache/hosted/pub.dartlang.org/permission_handler-5.0.1+1/ios/Classes/strategies/PhotoPermissionStrategy.m:39:13: warning: enumeration value 'PHAuthorizationStatusLimited' not handled in switch [-Wswitch] switch (authorizationStatus) { ^ /Users/buildeprograms/flutte.pub-cache/hosted/pub.dartlang.org/permission_handler-5.0.1+1/ios/Classes/strategies/PhotoPermissionStrategy.m:39:13: note: add missing switch cases switch (authorizationStatus) { ^ 1 warning generated. In file included from /Users/buildeprograms/flutte.pub-cache/hosted/pub.dartlang.org/fluttertoast-7.0.2/ios/Classes/UIView+Toast.m:26: /Users/buildeprograms/flutte.pub-cache/hosted/pub.dartlang.org/fluttertoast-7.0.2/ios/Classes/UIView+Toast.h:328:19: warning: empty paragraph passed to '@param' command [-Wdocumentation] @param sharedStyle ~~~~~~~~~~~~~~~^ /Users/buildeprograms/flutte.pub-cache/hosted/pub.dartlang.org/fluttertoast-7.0.2/ios/Classes/UIView+Toast.h:343:25: warning: empty paragraph passed to '@param' command [-Wdocumentation] @param allowTapToDismiss ~~~~~~~~~~~~~~~~~~~^ /Users/buildeprograms/flutte.pub-cache/hosted/pub.dartlang.org/fluttertoast-7.0.2/ios/Classes/UIView+Toast.h:343:9: warning: parameter 'allowTapToDismiss' not found in the function declaration [-Wdocumentation] @param allowTapToDismiss ^~~~~~~~~~~~~~~ /Users/buildeprograms/flutte.pub-cache/hosted/pub.dartlang.org/fluttertoast-7.0.2/ios/Classes/UIView+Toast.h:343:9: note: did you mean 'tapToDismissEnabled'? @param allowTapToDismiss ~~~~~~~~~~~~~~~~ tapToDismissEnabled /Users/buildeprograms/flutte.pub-cache/hosted/pub.dartlang.org/fluttertoast-7.0.2/ios/Classes/UIView+Toast.h:362:20: warning: empty paragraph passed to '@param' command [-Wdocumentation] @param queueEnabled ~~~~~~~~~~~~~~~~^ 4 warnings generated. In file included from /Users/buildeprograms/flutte.pub-cache/hosted/pub.dartlang.org/fluttertoast-7.0.2/ios/Classes/FluttertoastPlugin.m:2: /Users/buildeprograms/flutte.pub-cache/hosted/pub.dartlang.org/fluttertoast-7.0.2/ios/Classes/UIView+Toast.h:328:19: warning: empty paragraph passed to '@param' command [-Wdocumentation] @param sharedStyle ~~~~~~~~~~~~~^ /Users/buildeprograms/flutte.pub-cache/hosted/pub.dartlang.org/fluttertoast-7.0.2/ios/Classes/UIView+Toast.h:343:25: warning: empty paragraph passed to '@param' command [-Wdocumentation] @param allowTapToDismiss ~~~~~~~~~~~~~~~~~~~^ /Users/buildeprograms/flutte.pub-cache/hosted/pub.dartlang.org/fluttertoast-7.0.2/ios/Classes/UIView+Toast.h:343:9: warning: parameter 'allowTapToDismiss' not found in the function declaration [-Wdocumentation] @param allowTapToDismiss ^~~~~~~~~~~~~~~ /Users/buildeprograms/flutte.pub-cache/hosted/pub.dartlang.org/fluttertoast-7.0.2/ios/Classes/UIView+Toast.h:343:9: note: did you mean 'tapToDismissEnabled'? @param allowTapToDismiss ~~~~~~~~~~~~~~~~ tapToDismissEnabled /Users/buildeprograms/flutte.pub-cache/hosted/pub.dartlang.org/fluttertoast-7.0.2/ios/Classes/UIView+Toast.h:362:20: warning: empty paragraph passed to '@param' command [-Wdocumentation] @param queueEnabled ~~~~~~~~~~~~~~~~^ /Users/buildeprograms/flutte.pub-cache/hosted/pub.dartlang.org/fluttertoast-7.0.2/ios/Classes/FluttertoastPlugin.m:19:23: warning: unused variable 'viewController' [-Wunused-variable] UIViewController *viewController = ^ /Users/buildeprograms/flutte.pub-cache/hosted/pub.dartlang.org/fluttertoast-7.0.2/ios/Classes/FluttertoastPlugin.m:70:21: warning: unused variable 'topPadding' [-Wunused-variable] CGFloat topPadding = window.safeAreaInsets.top; ^ /Users/buildeprograms/flutte.pub-cache/hosted/pub.dartlang.org/fluttertoast-7.0.2/ios/Classes/FluttertoastPlugin.m:71:21: warning: unused variable 'bottomPadding' [-Wunused-variable] CGFloat bottomPadding = window.safeAreaInsets.bottom; ^ /Users/buildeprograms/flutte.pub-cache/hosted/pub.dartlang.org/fluttertoast-7.0.2/ios/Classes/FluttertoastPlugin.m:48:19: warning: unused variable 'size' [-Wunused-variable] NSNumber *size = call.arguments[@"size"]; ^ 8 warnings generated. In file included from /Users/buildeprograms/flutte.pub-cache/hosted/pub.dartlang.org/fluttertoast-7.0.2/ios/Classes/UIView+Toast.m:26: /Users/buildeprograms/flutte.pub-cache/hosted/pub.dartlang.org/fluttertoast-7.0.2/ios/Classes/UIView+Toast.h:328:19: warning: empty paragraph passed to '@param' command [-Wdocumentation] @param sharedStyle ~~~~~~~~~~~~~^ /Users/buildeprograms/flutte.pub-cache/hosted/pub.dartlang.org/fluttertoast-7.0.2/ios/Classes/UIView+Toast.h:343:25: warning: empty paragraph passed to '@param' command [-Wdocumentation] @param allowTapToDismiss ~~~~~~~~~~~~~~~~~~~^ /Users/buildeprograms/flutte.pub-cache/hosted/pub.dartlang.org/fluttertoast-7.0.2/ios/Classes/UIView+Toast.h:343:9: warning: parameter 'allowTapToDismiss' not found in the function declaration [-Wdocumentation] @param allowTapToDismiss ^~~~~~~~~~~~~~~ /Users/buildeprograms/flutte.pub-cache/hosted/pub.dartlang.org/fluttertoast-7.0.2/ios/Classes/UIView+Toast.h:343:9: note: did you mean 'tapToDismissEnabled'? @param allowTapToDismiss ~~~~~~~~~~~~~~~~ tapToDismissEnabled /Users/buildeprograms/flutte.pub-cache/hosted/pub.dartlang.org/fluttertoast-7.0.2/ios/Classes/UIView+Toast.h:362:20: warning: empty paragraph passed to '@param' command [-Wdocumentation] @param queueEnabled ~~~~~~~~~~~~~~~~^ 4 warnings generated. In file included from /Users/buildeprograms/flutte.pub-cache/hosted/pub.dartlang.org/fluttertoast-7.0.2/ios/Classes/FluttertoastPlugin.m:2: /Users/buildeprograms/flutte.pub-cache/hosted/pub.dartlang.org/fluttertoast-7.0.2/ios/Classes/UIView+Toast.h:328:19: warning: empty paragraph passed to '@param' command [-Wdocumentation] @param sharedStyle ~~~~~~~~~~~~~^ /Users/buildeprograms/flutte.pub-cache/hosted/pub.dartlang.org/fluttertoast-7.0.2/ios/Classes/UIView+Toast.h:343:25: warning: empty paragraph passed to '@param' command [-Wdocumentation] @param allowTapToDismiss ~~~~~~~~~~~~~~~~~~~^ /Users/buildeprograms/flutte.pub-cache/hosted/pub.dartlang.org/fluttertoast-7.0.2/ios/Classes/UIView+Toast.h:343:9: warning: parameter 'allowTapToDismiss' not found in the function declaration [-Wdocumentation] @param allowTapToDismiss ^~~~~~~~~~~~~~~ /Users/buildeprograms/flutte.pub-cache/hosted/pub.dartlang.org/fluttertoast-7.0.2/ios/Classes/UIView+Toast.h:343:9: note: did you mean 'tapToDismissEnabled'? @param allowTapToDismiss ~~~~~~~~~~~~~~~~ tapToDismissEnabled /Users/buildeprograms/flutte.pub-cache/hosted/pub.dartlang.org/fluttertoast-7.0.2/ios/Classes/UIView+Toast.h:362:20: warning: empty paragraph passed to '@param' command [-Wdocumentation] @param queueEnabled ~~~~~~~~~~~~~~~~^ /Users/buildeprograms/flutte.pub-cache/hosted/pub.dartlang.org/fluttertoas t-7.0.2/ios/Classes/FluttertoastPlugin.m:19:23: warning: unused variable 'viewController' [-Wunused-variable] UIViewController *viewController = ^ /Users/buildeprograms/flutte.pub-cache/hosted/pub.dartlang.org/fluttertoast-7.0.2/ios/Classes/FluttertoastPlugin.m:70:21: warning: unused variable 'topPadding' [-Wunused-variable] CGFloat topPadding = window.safeAreaInsets.top; ^ /Users/buildeprograms/flutte.pub-cache/hosted/pub.dartlang.org/fluttertoast-7.0.2/ios/Classes/FluttertoastPlugin.m:71:21: warning: unused variable 'bottomPadding' [-Wunused-variable] CGFloat bottomPadding = window.safeAreaInsets.bottom; ^ /Users/buildeprograms/flutte.pub-cache/hosted/pub.dartlang.org/fluttertoast-7.0.2/ios/Classes/FluttertoastPlugin.m:48:19: warning: unused variable 'size' [-Wunused-variable] NSNumber *size = call.arguments[@"size"]; ^ 8 warnings generated. /Users/buildeprograms/flutte.pub-cache/hosted/pub.dartlang.org/audioplayers-0.16.1/darwin/Classes/AudioplayersPlugin.m:89:37: warning: incompatible pointer types sending 'FlutterEngine *' to parameter of type 'NSObject * _Nonnull' [-Wincompatible-pointer-types] binaryMessenger:_headlessEngine]; ^~~~~~~~~~~~~ In module 'Flutter' imported from /Users/buildeprograms/flutte.pub-cache/hosted/pub.dartlang.org/audioplayers-0.16.1/darwin/Classes/AudioplayersPlugin.h:2: /Users/buildeclone/ios/FlutteFlutter.framework/Headers/FlutterChannels.h:178:74: note: passing argument to parameter 'messenger' here binaryMessenger:(NSObject)messenger; ^ /Users/buildeprograms/flutte.pub-cache/hosted/pub.dartlang.org/audioplayers-0.16.1/darwin/Classes/AudioplayersPlugin.m:375:81: warning: 'changePlaybackPositionCommand' is only available on iOS 9.1 or newer [-Wunguarded-availability] MPRemoteCommand *changePlaybackPositionCommand = [remoteCommandCenter changePlaybackPositionCommand]; ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ In module 'MediaPlayer' imported from /Users/buildeprograms/flutte.pub-cache/hosted/pub.dartlang.org/audioplayers-0.16.1/darwin/Classes/AudioplayersPlugin.m:7: /Applications/Xcode-12.app/Contents/DevelopePlatforms/iPhoneOS.platform/DevelopeSDKs/iPhoneOS14.0.sdk/System/Library/Frameworks/MediaPlayer.framework/Headers/MPRemoteCommandCenter.h:47:66: note: 'changePlaybackPositionCommand' has been marked as being introduced in iOS 9.1 here, but the deployment target is iOS 8.0.0 @property (nonatomic, readonly) MPChangePlaybackPositionCommand *changePlaybackPositionCommand MP_API(ios(9.1), macos(10.12.2)); ^ /Users/buildeprograms/flutte.pub-cache/hosted/pub.dartlang.org/audioplayers-0.16.1/darwin/Classes/AudioplayersPlugin.m:375:81: note: enclose 'changePlaybackPositionCommand' in an @available check to silence this warning MPRemoteCommand *changePlaybackPositionCommand = [remoteCommandCenter changePlaybackPositionCommand]; ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 2 warnings generated. /Users/buildeprograms/flutte.pub-cache/hosted/pub.dartlang.org/audioplayers-0.16.1/darwin/Classes/AudioplayersPlugin.m:89:37: warning: incompatible pointer types sending 'FlutterEngine *' to parameter of type 'NSObject * _Nonnull' [-Wincompatible-pointer-types] binaryMessenger:_headlessEngine]; ~~~~~~~~~~~~~~ In module 'Flutter' imported from /Users/buildeprograms/flutte.pub-cache/hosted/pub.dartlang.org/audioplayers-0.16.1/darwin/Classes/AudioplayersPlugin.h:2: /Users/buildeclone/ios/FlutteFlutter.framework/Headers/FlutterChannels.h:178:74: note: passing argument to parameter 'messenger' here binaryMessenger:(NSObject)messenger; ^ /Users/buildeprograms/flutte.pub-cache/hosted/pub.dartlang.org/audioplayers-0.16.1/darwin/Classes/AudioplayersPlugin.m:375:81: warning: 'changePlaybackPositionCommand' is only available on iOS 9.1 or newer [-Wunguarded-availability] MPRemoteCommand *changePlaybackPositionCommand = [remoteCommandCenter changePlaybackPositionCommand]; ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ In module 'MediaPlayer' imported from /Users/buildeprograms/flutte.pub-cache/hosted/pub.dartlang.org/audioplayers-0.16.1/darwin/Classes/AudioplayersPlugin.m:7: /Applications/Xcode-12.app/Contents/DevelopePlatforms/iPhoneOS.platform/DevelopeSDKs/iPhoneOS14.0.sdk/System/Library/Frameworks/MediaPlayer.framework/Headers/MPRemoteCommandCenter.h:47:66: note: 'changePlaybackPositionCommand' has been marked as being introduced in iOS 9.1 here, but the deployment target is iOS 8.0.0 @property (nonatomic, readonly) MPChangePlaybackPositionCommand *changePlaybackPositionCommand MP_API(ios(9.1), macos(10.12.2)); ^ /Users/buildeprograms/flutte.pub-cache/hosted/pub.dartlang.org/audioplayers-0.16.1/darwin/Classes/AudioplayersPlugin.m:375:81: note: enclose 'changePlaybackPositionCommand' in an @available check to silence this warning MPRemoteCommand *changePlaybackPositionCommand = [remoteCommandCenter changePlaybackPositionCommand]; ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 2 warnings generated. /Users/buildeprograms/flutte.pub-cache/hosted/pub.dartlang.org/audio_recorder-1.0.2/ios/Classes/SwiftAudioRecorderPlugin.swift:39:108: error: 'AVAudioSessionCategoryOptions' has been renamed to 'AVAudioSession.CategoryOptions' try AVAudioSession.sharedInstance().setCategory(AVAudioSessionCategoryPlayAndRecord, with: AVAudioSessionCategoryOptions.defaultToSpeaker) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ AVAudioSession.CategoryOptions AVFoundation.AVAudioSessionCategoryOptions:2:18: note: 'AVAudioSessionCategoryOptions' was obsoleted in Swift 4.2 public typealias AVAudioSessionCategoryOptions = AVAudioSession.CategoryOptions ^ /Users/buildeprograms/flutte.pub-cache/hosted/pub.dartlang.org/audio_recorder-1.0.2/ios/Classes/SwiftAudioRecorderPlugin.swift:67:52: error: cannot call value of non-function type 'AVAudioSession.RecordPermission' switch AVAudioSession.sharedInstance().recordPermission(){ ^ ~~
    Command CompileSwift failed with a nonzero exit code note: Using new build system note: Building targets in parallel note: Planning build note: Constructing build description warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.0.99. (in target 'connectivity' from project 'Pods') warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.0.99. (in target 'emoji_picker' from project 'Pods') warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.0.99. (in target 'webview_flutter' from project 'Pods') w 
    arning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.0.99. (in target 'wakelock' from project 'Pods') warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.0.99. (in target 'video_player' from project 'Pods') warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.0.99. (in target 'url_launcher' from project 'Pods') warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.0.99. (in target 'sqflite' from project 'Pods') warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.0.99. (in target 'shared_preferences' from project 'Pods') warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.0.99. (in target 'screen' from project 'Pods') warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.0.99. (in target 'permission_handler' from project 'Pods') warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.0.99. (in target 'path_provider' from project 'Pods') warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.0.99. (in target 'package_info' from project 'Pods') warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.0.99. (in target 'nanopb' from project 'Pods') warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.0.99. (in target 'image_picker' from project 'Pods') warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.0.99. (in target 'image_cropper' from project 'Pods') warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.0.99. (in target 'fluttertoast' from project 'Pods') warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.0.99. (in target 'flutter_plugin_android_lifecycle' from project 'Pods') warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.0.99. (in target 'firebase_crashlytics' from project 'Pods') warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.0.99. (in target 'firebase_core' from project 'Pods') warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.0.99. (in target 'file_picker' from project 'Pods') warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.0.99. (in target 'audioplayers' from project 'Pods') warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.0.99. (in target 'audio_recorder' from project 'Pods') warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.0.99. (in target 'TOCropViewController-TOCropViewControllerBundle' from project 'Pods') warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.0.99. (in target 'TOCropViewController' from project 'Pods') warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.0.99. (in target 'SwiftyGif' from project 'Pods') warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.0.99. (in target 'SDWebImage' from project 'Pods') warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.0.99. (in target 'Runner' from project 'Runner') warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.0.99. (in target 'Reachability' from project 'Pods') warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.0.99. (in target 'GoogleUtilities' from project 'Pods') warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.0.99. (in target 'GoogleDataTransportCCTSupport' from project 'Pods') warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.0.99. (in target 'GoogleDataTransport' from project 'Pods') warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.0.99. (in target 'FirebaseInstallations' from project 'Pods') warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.0.99. (in target 'FirebaseCrashlytics' from project 'Pods') warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.0.99. (in target 'FirebaseCoreDiagnostics' from project 'Pods') warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.0.99. (in target 'FirebaseCore' from project 'Pods') warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.0.99. (in target 'FMDB' from project 'Pods') warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.0.99. (in target 'path_provider_macos' from project 'Pods') warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.0.99. (in target 'connectivity_macos' from project 'Pods') warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.0.99. (in target 'Firebase' from project 'Pods') warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.0.99. (in target 'shared_preferences_macos' from project 'Pods') warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.0.99. (in target 'firebase_core_web' from project 'Pods') warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.0.99. (in target 'connectivity_for_web' from project 'Pods') warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0
    to 14.0.99. (in target 'shared_preferences_web' from project 'Pods') warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.0.99. (in target 'path_provider_linux' from project 'Pods') warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.0.99. (in target 'video_player_web' from project 'Pods') warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.0.99. (in target 'url_launcher_web' from project 'Pods') warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.0.99. (in target 'url_launcher_macos' from project 'Pods') warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.0.99. (in target 'url_launcher_linux' from project 'Pods') warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.0.99. (in target 'shared_preferences_linux' from project 'Pods') warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.0.99. (in target 'FirebaseCoreDiagnosticsInterop' from project 'Pods') warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.0.99. (in target 'FirebaseAnalyticsInterop' from project 'Pods') warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.0.99. (in target 'Flutter' from project 'Pods')
    Encountered error while building for device.
    Build failed :| Failed to build for iOS ```
    submitted by SepehrAzizi to flutterhelp [link] [comments]

    First Time Going Through Coding Interviews?

    This post draws on my personal experiences and challenges over the past term at school, which I entered with hardly any knowledge of DSA (data structures and algorithms) and problem-solving strategies. As a self-taught programmer, I was a lot more familiar and comfortable with general programming, such as object-oriented programming, than with the problem-solving skills required in DSA questions.
    This post reflects my journey throughout the term and the resources I turned to in order to quickly improve for my coding interview.
    Here're some common questions and answers
    What's the interview process like at a tech company?
    Good question. It's actually pretty different from most other companies.

    (What It's Like To Interview For A Coding Job

    First time interviewing for a tech job? Not sure what to expect? This article is for you.

    Here are the usual steps:

    1. First, you’ll do a non-technical phone screen.
    2. Then, you’ll do one or a few technical phone interviews.
    3. Finally, the last step is an onsite interview.
    Some companies also throw in a take-home code test—sometimes before the technical phone interviews, sometimes after.
    Let’s walk through each of these steps.

    The non-technical phone screen

    This first step is a quick call with a recruiter—usually just 10–20 minutes. It's very casual.
    Don’t expect technical questions. The recruiter probably won’t be a programmer.
    The main goal is to gather info about your job search. Stuff like:

    1. Your timeline. Do you need to sign an offer in the next week? Or are you trying to start your new job in three months?
    2. What’s most important to you in your next job. Great team? Flexible hours? Interesting technical challenges? Room to grow into a more senior role?
    3. What stuff you’re most interested in working on. Front end? Back end? Machine learning?
    Be honest about all this stuff—that’ll make it easier for the recruiter to get you what you want.
    One exception to that rule: If the recruiter asks you about your salary expectations on this call, best not to answer. Just say you’d rather talk about compensation after figuring out if you and the company are a good fit. This’ll put you in a better negotiating position later on.

    The technical phone interview(s)

    The next step is usually one or more hour-long technical phone interviews.
    Your interviewer will call you on the phone or tell you to join them on Skype or Google Hangouts. Make sure you can take the interview in a quiet place with a great internet connection. Consider grabbing a set of headphones with a good microphone or a bluetooth earpiece. Always test your hardware beforehand!
    The interviewer will want to watch you code in real time. Usually that means using a web-based code editor like Coderpad or collabedit. Run some practice problems in these tools ahead of time, to get used to them. Some companies will just ask you to share your screen through Google Hangouts or Skype.
    Turn off notifications on your computer before you get started—especially if you’re sharing your screen!
    Technical phone interviews usually have three parts:

    1. Beginning chitchat (5–10 minutes)
    2. Technical challenges (30–50 minutes)
    3. Your turn to ask questions (5–10 minutes)
    The beginning chitchat is half just to help your relax, and half actually part of the interview. The interviewer might ask some open-ended questions like:

    1. Tell me about yourself.
    2. Tell me about something you’ve built that you’re particularly proud of.
    3. I see this project listed on your resume—tell me more about that.
    You should be able to talk at length about the major projects listed on your resume. What went well? What didn’t? How would you do things differently now?
    Then come the technical challenges—the real meet of the interview. You’ll spend most of the interview on this. You might get one long question, or several shorter ones.
    What kind of questions can you expect? It depends.
    Startups tend to ask questions aimed towards building or debugging code. (“Write a function that takes two rectangles and figures out if they overlap.”). They’ll care more about progress than perfection.
    Larger companies will want to test your general know-how of data structures and algorithms (“Write a function that checks if a binary tree is ‘balanced’ in O(n)O(n) ↴ time.”). They’ll care more about how you solve and optimize a problem.
    With these types of questions, the most important thing is to be communicating with your interviewer throughout. You'll want to "think out loud" as you work through the problem. For more info, check out our more detailed step-by-step tips for coding interviews.
    If the role requires specific languages or frameworks, some companies will ask trivia-like questions (“In Python, what’s the ‘global interpreter lock’?”).
    After the technical questions, your interviewer will open the floor for you to ask them questions. Take some time before the interview to comb through the company’s website. Think of a few specific questions about the company or the role. This can really make you stand out.
    When you’re done, they should give you a timeframe on when you’ll hear about next steps. If all went well, you’ll either get asked to do another phone interview, or you’ll be invited to their offices for an onsite.

    The onsite interview

    An onsite interview happens in person, at the company’s office. If you’re not local, it’s common for companies to pay for a flight and hotel room for you.
    The onsite usually consists of 2–6 individual, one-on-one technical interviews (usually in a small conference room). Each interview will be about an hour and have the same basic form as a phone screen—technical questions, bookended by some chitchat at the beginning and a chance for you to ask questions at the end.
    The major difference between onsite technical interviews and phone interviews though: you’ll be coding on a whiteboard.
    This is awkward at first. No autocomplete, no debugging tools, no delete button…ugh. The good news is, after some practice you get used to it. Before your onsite, practice writing code on a whiteboard (in a pinch, a pencil and paper are fine). Some tips:

    1. Start in the top-most left corner of the whiteboard. This gives you the most room. You’ll need more space than you think.
    2. Leave a blank line between each line as you write your code. Makes it much easier to add things in later.
    3. Take an extra second to decide on your variable names. Don’t rush this part. It might seem like a waste of time, but using more descriptive variable names ultimately saves you time because it makes you less likely to get confused as you write the rest of your code.
    If a technical phone interview is a sprint, an onsite is a marathon. The day can get really long. Best to keep it open—don’t make other plans for the afternoon or evening.
    When things go well, you’ wrap-up by chatting with the CEO or some other director. This is half an interview, half the company trying to impress you. They may invite you to get drinks with the team after hours.
    All told, a long day of onsite interviews could look something like this:

    If they let you go after just a couple interviews, it’s usually a sign that they’re going to pass on you. That’s okay—it happens!
    There are are a lot of easy things you can do the day before and morning of your interview to put yourself in the best possible mindset. Check out our piece on what to do in the 24 hours before your onsite coding interview.

    The take-home code test

    Code tests aren’t ubiquitous, but they seem to be gaining in popularity. They’re far more common at startups, or places where your ability to deliver right away is more important than your ability to grow.
    You’ll receive a description of an app or service, a rough time constraint for writing your code, and a deadline for when to turn it in. The deadline is usually negotiable.
    Here's an example problem:
    Write a basic “To-Do” app. Unit test the core functionality. As a bonus, add a “reminders” feature. Try to spend no more than 8 hours on it, and send in what you have by Friday with a small write-up.
    Take a crack at the “bonus” features if they include any. At the very least, write up how you would implement it.
    If they’re hiring for people with knowledge of a particular framework, they might tell you what tech to use. Otherwise, it’ll be up to you. Use what you’re most comfortable with. You want this code to show you at your best.
    Some places will offer to pay you for your time. It's rare, but some places will even invite you to work with them in their office for a few days, as a "trial.")
    Do I need to know this "big O" stuff?
    Big O notation is the language we use for talking about the efficiency of data structures and algorithms.
    Will it come up in your interviews? Well, it depends. There are different types of interviews.
    There’s the classic algorithmic coding interview, sometimes called the “Google-style whiteboard interview.” It’s focused on data structures and algorithms (queues and stacks, binary search, etc).
    That’s what our full course prepares you for. It's how the big players interview. Google, Facebook, Amazon, Microsoft, Oracle, LinkedIn, etc.
    For startups and smaller shops, it’s a mixed bag. Most will ask at least a few algorithmic questions. But they might also include some role-specific stuff, like Java questions or SQL questions for a backend web engineer. They’ll be especially interested in your ability to ship code without much direction. You might end up doing a code test or pair-programming exercise instead of a whiteboarding session.
    To make sure you study for the right stuff, you should ask your recruiter what to expect. Send an email with a question like, “Is this interview going to cover data structures and algorithms? Or will it be more focused around coding in X language.” They’ll be happy to tell you.
    If you've never learned about data structures and algorithms, or you're feeling a little rusty, check out our Intuitive Guide to Data Structures and Algorithms.
    Which programming language should I use?
    Companies usually let you choose, in which case you should use your most comfortable language. If you know a bunch of languages, prefer one that lets you express more with fewer characters and fewer lines of code, like Python or Ruby. It keeps your whiteboard cleaner.
    Try to stick with the same language for the whole interview, but sometimes you might want to switch languages for a question. E.g., processing a file line by line will be far easier in Python than in C++.
    Sometimes, though, your interviewer will do this thing where they have a pet question that’s, for example, C-specific. If you list C on your resume, they’ll ask it.
    So keep that in mind! If you’re not confident with a language, make that clear on your resume. Put your less-strong languages under a header like ‘Working Knowledge.’
    What should I wear?
    A good rule of thumb is to dress a tiny step above what people normally wear to the office. For most west coast tech companies, the standard digs are just jeans and a t-shirt. Ask your recruiter what the office is like if you’re worried about being too casual.
    Should I send a thank-you note?
    Thank-you notes are nice, but they aren’t really expected. Be casual if you send one. No need for a hand-calligraphed note on fancy stationery. Opt for a short email to your recruiter or the hiring manager. Thank them for helping you through the process, and ask them to relay your thanks to your interviewers.
    1) Coding Interview Tips
    How to get better at technical interviews without practicing
    Chitchat like a pro.
    Before diving into code, most interviewers like to chitchat about your background. They're looking for:

    You should have at least one:

    Nerd out about stuff. Show you're proud of what you've done, you're amped about what they're doing, and you have opinions about languages and workflows.
    Communicate.
    Once you get into the coding questions, communication is key. A candidate who needed some help along the way but communicated clearly can be even better than a candidate who breezed through the question.
    Understand what kind of problem it is. There are two types of problems:

    1. Coding. The interviewer wants to see you write clean, efficient code for a problem.
    2. Chitchat. The interviewer just wants you to talk about something. These questions are often either (1) high-level system design ("How would you build a Twitter clone?") or (2) trivia ("What is hoisting in Javascript?"). Sometimes the trivia is a lead-in for a "real" question e.g., "How quickly can we sort a list of integers? Good, now suppose instead of integers we had . . ."
    If you start writing code and the interviewer just wanted a quick chitchat answer before moving on to the "real" question, they'll get frustrated. Just ask, "Should we write code for this?"
    Make it feel like you're on a team. The interviewer wants to know what it feels like to work through a problem with you, so make the interview feel collaborative. Use "we" instead of "I," as in, "If we did a breadth-first search we'd get an answer in O(n)O(n) time." If you get to choose between coding on paper and coding on a whiteboard, always choose the whiteboard. That way you'll be situated next to the interviewer, facing the problem (rather than across from her at a table).
    Think out loud. Seriously. Say, "Let's try doing it this way—not sure yet if it'll work." If you're stuck, just say what you're thinking. Say what might work. Say what you thought could work and why it doesn't work. This also goes for trivial chitchat questions. When asked to explain Javascript closures, "It's something to do with scope and putting stuff in a function" will probably get you 90% credit.
    Say you don't know. If you're touching on a fact (e.g., language-specific trivia, a hairy bit of runtime analysis), don't try to appear to know something you don't. Instead, say "I'm not sure, but I'd guess $thing, because...". The because can involve ruling out other options by showing they have nonsensical implications, or pulling examples from other languages or other problems.
    Slow the eff down. Don't confidently blurt out an answer right away. If it's right you'll still have to explain it, and if it's wrong you'll seem reckless. You don't win anything for speed and you're more likely to annoy your interviewer by cutting her off or appearing to jump to conclusions.
    Get unstuck.
    Sometimes you'll get stuck. Relax. It doesn't mean you've failed. Keep in mind that the interviewer usually cares more about your ability to cleverly poke the problem from a few different angles than your ability to stumble into the correct answer. When hope seems lost, keep poking.
    Draw pictures. Don't waste time trying to think in your head—think on the board. Draw a couple different test inputs. Draw how you would get the desired output by hand. Then think about translating your approach into code.
    Solve a simpler version of the problem. Not sure how to find the 4th largest item in the set? Think about how to find the 1st largest item and see if you can adapt that approach.
    Write a naive, inefficient solution and optimize it later. Use brute force. Do whatever it takes to get some kind of answer.
    Think out loud more. Say what you know. Say what you thought might work and why it won't work. You might realize it actually does work, or a modified version does. Or you might get a hint.
    Wait for a hint. Don't stare at your interviewer expectantly, but do take a brief second to "think"—your interviewer might have already decided to give you a hint and is just waiting to avoid interrupting.
    Think about the bounds on space and runtime. If you're not sure if you can optimize your solution, think about it out loud. For example:

    Get your thoughts down.
    It's easy to trip over yourself. Focus on getting your thoughts down first and worry about the details at the end.
    Call a helper function and keep moving. If you can't immediately think of how to implement some part of your algorithm, big or small, just skip over it. Write a call to a reasonably-named helper function, say "this will do X" and keep going. If the helper function is trivial, you might even get away with never implementing it.
    Don't worry about syntax. Just breeze through it. Revert to English if you have to. Just say you'll get back to it.
    Leave yourself plenty of room. You may need to add code or notes in between lines later. Start at the top of the board and leave a blank line between each line.
    Save off-by-one checking for the end. Don't worry about whether your for loop should have "<<" or "<=<=." Write a checkmark to remind yourself to check it at the end. Just get the general algorithm down.
    Use descriptive variable names. This will take time, but it will prevent you from losing track of what your code is doing. Use names_to_phone_numbers instead of nums. Imply the type in the name. Functions returning booleans should start with "is_*". Vars that hold a list should end with "s." Choose standards that make sense to you and stick with them.
    Clean up when you're done.
    Walk through your solution by hand, out loud, with an example input. Actually write down what values the variables hold as the program is running—you don't win any brownie points for doing it in your head. This'll help you find bugs and clear up confusion your interviewer might have about what you're doing.
    Look for off-by-one errors. Should your for loop use a "<=<=" instead of a "<<"?
    Test edge cases. These might include empty sets, single-item sets, or negative numbers. Bonus: mention unit tests!
    Don't be boring. Some interviewers won't care about these cleanup steps. If you're unsure, say something like, "Then I'd usually check the code against some edge cases—should we do that next?"
    Practice.
    In the end, there's no substitute for running practice questions.
    Actually write code with pen and paper. Be honest with yourself. It'll probably feel awkward at first. Good. You want to get over that awkwardness now so you're not fumbling when it's time for the real interview.

    2) Tricks For Getting Unstuck During a Coding Interview
    Getting stuck during a coding interview is rough.
    If you weren’t in an interview, you might take a break or ask Google for help. But the clock is ticking, and you don’t have Google.
    You just have an empty whiteboard, a smelly marker, and an interviewer who’s looking at you expectantly. And all you can think about is how stuck you are.
    You need a lifeline for these moments—like a little box that says “In Case of Emergency, Break Glass.”
    Inside that glass box? A list of tricks for getting unstuck. Here’s that list of tricks.
    When you’re stuck on getting started
    1) Write a sample input on the whiteboard and turn it into the correct output "by hand." Notice the process you use. Look for patterns, and think about how to implement your process in code.
    Trying to reverse a string? Write “hello” on the board. Reverse it “by hand”—draw arrows from each character’s current position to its desired position.
    Notice the pattern: it looks like we’re swapping pairs of characters, starting from the outside and moving in. Now we’re halfway to an algorithm.
    2) Solve a simpler version of the problem. Remove or simplify one of the requirements of the problem. Once you have a solution, see if you can adapt that approach for the original question.
    Trying to find the k-largest element in a set? Walk through finding the largest element, then the second largest, then the third largest. Generalizing from there to find the k-largest isn’t so bad.
    3) Start with an inefficient solution. Even if it feels stupidly inefficient, it’s often helpful to start with something that’ll return the right answer. From there, you just have to optimize your solution. Explain to your interviewer that this is only your first idea, and that you suspect there are faster solutions.
    Suppose you were given two lists of sorted numbers and asked to find the median of both lists combined. It’s messy, but you could simply:

    1. Concatenate the arrays together into a new array.
    2. Sort the new array.
    3. Return the value at the middle index.
    Notice that you could’ve also arrived at this algorithm by using trick (2): Solve a simpler version of the problem. “How would I find the median of one sorted list of numbers? Just grab the item at the middle index. Now, can I adapt that approach for getting the median of two sorted lists?”
    When you’re stuck on finding optimizations
    1) Look for repeat work. If your current solution goes through the same data multiple times, you’re doing unnecessary repeat work. See if you can save time by looking through the data just once.
    Say that inside one of your loops, there’s a brute-force operation to find an element in an array. You’re repeatedly looking through items that you don’t have to. Instead, you could convert the array to a lookup table to dramatically improve your runtime.
    2) Look for hints in the specifics of the problem. Is the input array sorted? Is the binary tree balanced? Details like this can carry huge hints about the solution. If it didn’t matter, your interviewer wouldn’t have brought it up. It’s a strong sign that the best solution to the problem exploits it.
    Suppose you’re asked to find the first occurrence of a number in a sorted array. The fact that the array is sorted is a strong hint—take advantage of that fact by using a binary search.

    Sometimes interviewers leave the question deliberately vague because they want you to ask questions to unearth these important tidbits of context. So ask some questions at the beginning of the problem.
    3) Throw some data structures at the problem. Can you save time by using the fast lookups of a hash table? Can you express the relationships between data points as a graph? Look at the requirements of the problem and ask yourself if there’s a data structure that has those properties.
    4) Establish bounds on space and runtime. Think out loud about the parameters of the problem. Try to get a sense for how fast your algorithm could possibly be:

    When All Else Fails
    1) Make it clear where you are. State what you know, what you’re trying to do, and highlight the gap between the two. The clearer you are in expressing exactly where you’re stuck, the easier it is for your interviewer to help you.
    2) Pay attention to your interviewer. If she asks a question about something you just said, there’s probably a hint buried in there. Don’t worry about losing your train of thought—drop what you’re doing and dig into her question.
    Relax. You’re supposed to get stuck.
    Interviewers choose hard problems on purpose. They want to see how you poke at a problem you don’t immediately know how to solve.
    Seriously. If you don’t get stuck and just breeze through the problem, your interviewer’s evaluation might just say “Didn’t get a good read on candidate’s problem-solving process—maybe she’d already seen this interview question before?”
    On the other hand, if you do get stuck, use one of these tricks to get unstuck, and communicate clearly with your interviewer throughout...that’s how you get an evaluation like, “Great problem-solving skills. Hire.”

    3) Fixing Impostor Syndrome in Coding Interviews
    “It's a fluke that I got this job interview...”
    “I studied for weeks, but I’m still not prepared...”
    “I’m not actually good at this. They’re going to see right through me...”
    If any of these thoughts resonate with you, you're not alone. They are so common they have a name: impostor syndrome.
    It’s that feeling like you’re on the verge of being exposed for what you really are—an impostor. A fraud.
    Impostor syndrome is like kryptonite to coding interviews. It makes you give up and go silent.
    You might stop asking clarifying questions because you’re afraid they’ll sound too basic. Or you might neglect to think out loud at the whiteboard, fearing you’ll say something wrong and sound incompetent.
    You know you should speak up, but the fear of looking like an impostor makes that really, really hard.
    Here’s the good news: you’re not an impostor. You just feel like an impostor because of some common cognitive biases about learning and knowledge.
    Once you understand these cognitive biases—where they come from and how they work—you can slowly fix them. You can quiet your worries about being an impostor and keep those negative thoughts from affecting your interviews.

    Everything you could know

    Here’s how impostor syndrome works.
    Software engineering is a massive field. There’s a huge universe of things you could know. Huge.
    In comparison to the vast world of things you could know, the stuff you actually know is just a tiny sliver:
    That’s the first problem. It feels like you don’t really know that much, because you only know a tiny sliver of all the stuff there is to know.

    The expanding universe

    It gets worse: counterintuitively, as you learn more, your sliver of knowledge feels like it's shrinking.
    That's because you brush up against more and more things you don’t know yet. Whole disciplines like machine learning, theory of computation, and embedded systems. Things you can't just pick up in an afternoon. Heavy bodies of knowledge that take months to understand.
    So the universe of things you could know seems to keep expanding faster and faster—much faster than your tiny sliver of knowledge is growing. It feels like you'll never be able to keep up.

    What everyone else knows

    Here's another common cognitive bias: we assume that because something is easy for us, it must be easy for everyone else. So when we look at our own skills, we assume they're not unique. But when we look at other people's skills, we notice the skills they have that we don't have.
    The result? We think everyone’s knowledge is a superset of our own:
    This makes us feel like everyone else is ahead of us. Like we're always a step behind.
    But the truth is more like this:
    There's a whole area of stuff you know that neither Aysha nor Bruno knows. An area you're probably blind to, because you're so focused on the stuff you don't know.

    We’ve all had flashes of realizing this. For me, it was seeing the back end code wizard on my team—the one that always made me feel like an impostor—spend an hour trying to center an image on a webpage.

    It's a problem of focus

    Focusing on what you don't know causes you to underestimate what you do know. And that's what causes impostor syndrome.
    By looking at the vast (and expanding) universe of things you could know, you feel like you hardly know anything.
    And by looking at what Aysha and Bruno know that you don't know, you feel like you're a step behind.
    And interviews make you really focus on what you don't know. You focus on what could go wrong. The knowledge gaps your interviewers might find. The questions you might not know how to answer.
    But remember:
    Just because Aysha and Bruno know some things you don't know, doesn't mean you don't also know things Aysha and Bruno don't know.
    And more importantly, everyone's body of knowledge is just a teeny-tiny sliver of everything they could learn. We all have gaps in our knowledge. We all have interview questions we won't be able to answer.
    You're not a step behind. You just have a lot of stuff you don't know yet. Just like everyone else.

    4) The 24 Hours Before Your Interview

    Feeling anxious? That’s normal. Your body is telling you you’re about to do something that matters.

    The twenty-four hours before your onsite are about finding ways to maximize your performance. Ideally, you wanna be having one of those days, where elegant code flows effortlessly from your fingertips, and bugs dare not speak your name for fear you'll squash them.
    You need to get your mind and body in The Zone™ before you interview, and we've got some simple suggestions to help.
    5) Why You're Hitting Dead Ends In Whiteboard Interviews

    The coding interview is like a maze

    Listening vs. holding your train of thought

    Finally! After a while of shooting in the dark and frantically fiddling with sample inputs on the whiteboard, you've came up with an algorithm for solving the coding question your interviewer gave you.
    Whew. Such a relief to have a clear path forward. To not be flailing anymore.
    Now you're cruising, getting ready to code up your solution.
    When suddenly, your interviewer throws you a curve ball.
    "What if we thought of the problem this way?"
    You feel a tension we've all felt during the coding interview:
    "Try to listen to what they're saying...but don't lose your train of thought...ugh, I can't do both!"
    This is a make-or-break moment in the coding interview. And so many people get it wrong.
    Most candidates end up only half understanding what their interviewer is saying. Because they're only half listening. Because they're desperately clinging to their train of thought.
    And it's easy to see why. For many of us, completely losing track of what we're doing is one of our biggest coding interview fears. So we devote half of our mental energy to clinging to our train of thought.
    To understand why that's so wrong, we need to understand the difference between what we see during the coding interview and what our interviewer sees.

    The programming interview maze

    Working on a coding interview question is like walking through a giant maze.
    You don't know anything about the shape of the maze until you start wandering around it. You might know vaguely where the solution is, but you don't know how to get there.
    As you wander through the maze, you might find a promising path (an approach, a way to break down the problem). You might follow that path for a bit.
    Suddenly, your interviewer suggests a different path:
    But from what you can see so far of the maze, your approach has already gotten you halfway there! Losing your place on your current path would mean a huge step backwards. Or so it seems.
    That's why people hold onto their train of thought instead of listening to their interviewer. Because from what they can see, it looks like they're getting somewhere!
    But here's the thing: your interviewer knows the whole maze. They've asked this question 100 times.

    I'm not exaggerating: if you interview candidates for a year, you can easily end up asking the same question over 100 times.
    So if your interviewer is suggesting a certain path, you can bet it leads to an answer.
    And your seemingly great path? There's probably a dead end just ahead that you haven't seen yet:
    Or it could just be a much longer route to a solution than you think it is. That actually happens pretty often—there's an answer there, but it's more complicated than you think.

    Hitting a dead end is okay. Failing to listen is not.

    Your interviewer probably won't fault you for going down the wrong path at first. They've seen really smart engineers do the same thing. They understand it's because you only have a partial view of the maze.
    They might have let you go down the wrong path for a bit to see if you could keep your thinking organized without help. But now they want to rush you through the part where you discover the dead end and double back. Not because they don't believe you can manage it yourself. But because they want to make sure you have enough time to finish the question.
    But here's something they will fault you for: failing to listen to them. Nobody wants to work with an engineer who doesn't listen.
    So when you find yourself in that crucial coding interview moment, when you're torn between holding your train of thought and considering the idea your interviewer is suggesting...remember this:
    Listening to your interviewer is the most important thing.
    Take what they're saying and run with it. Think of the next steps that follow from what they're saying.
    Even if it means completely leaving behind the path you were on. Trust the route your interviewer is pointing you down.
    Because they can see the whole maze.
    6) How To Get The Most Out Of Your Coding Interview Practice Sessions
    When you start practicing for coding interviews, there’s a lot to cover. You’ll naturally wanna brush up on technical questions. But how you practice those questions will make a big difference in how well you’re prepared.
    Here’re a few tips to make sure you get the most out of your practice sessions.
    Track your weak spots
    One of the hardest parts of practicing is knowing what to practice. Tracking what you struggle with helps answer that question.
    So grab a fresh notebook. After each question, look back and ask yourself, “What did I get wrong about this problem at first?” Take the time to write down one or two things you got stuck on, and what helped you figure them out. Compare these notes to our tips for getting unstuck.
    After each full practice session, read through your entire running list. Read it at the beginning of each practice session too. This’ll add a nice layer of rigor to your practice, so you’re really internalizing the lessons you’re learning.
    Use an actual whiteboard
    Coding on a whiteboard is awkward at first. You have to write out every single character, and you can’t easily insert or delete blocks of code.
    Use your practice sessions to iron out that awkwardness. Run a few problems on a piece of paper or, if you can, a real whiteboard. A few helpful tips for handwriting code:

    Set a timer
    Get a feel for the time pressure of an actual interview. You should be able to finish a problem in 30–45 minutes, including debugging your code at the end.
    If you’re just starting out and the timer adds too much stress, put this technique on the shelf. Add it in later as you start to get more comfortable with solving problems.
    Think out loud
    Like writing code on a whiteboard, this is an acquired skill. It feels awkward at first. But your interviewer will expect you to think out loud during the interview, so you gotta power through that awkwardness.
    A good trick to get used to talking out loud: Grab a buddy. Another engineer would be great, but you can also do this with a non-technical friend.
    Have your buddy sit in while you talk through a problem. Better yet—try loading up one of our questions on an iPad and giving that to your buddy to use as a script!
    Set aside a specific time of day to practice.
    Give yourself an hour each day to practice. Commit to practicing around the same time, like after you eat dinner. This helps you form a stickier habit of practicing.
    Prefer small, daily doses of practice to doing big cram sessions every once in a while. Distributing your practice sessions helps you learn more with less time and effort in the long run.
    part -2 will be upcoming in another post !
    submitted by Cyberrockz to u/Cyberrockz [link] [comments]

    How to install IQ Option app on android and iOS - Binary ... Step by step to make use of binary bot on android phone How To Use MetaTrader 4 - For Binary Options Trading - YouTube 2 Minutes Strategy Binary Options 2020 (IQ Options) - YouTube Smartphone Tutorial for Mobile Trading On NADEX..  #TeamAlliance Trading on Nadex APP How to trade binary options in Nadex for profit step by ...

    Binomo is a binary options broker with a high-end trading platform with the ability to trade binary options, CFDs, Forex, and cryptocurrency. Binomo is based out of St. Vincent and the Grenadines and they are regulated by the IFC (International Finance Commission). Since Binomo is a Category A member of the IFC, they have deposit insurance of up to $20,000 for all clients. Mobile devices make binary options trading accessible to more people in a much more user-friendly, less time-consuming experience. From attracting greater rewards to having more flexibility, there are many reasons that mobile trading is preferable to traditional methods. Trading on The go. Wherever you are, as long as you have a mobile device and an internet connection, you can trade. You don ... Thankfully you can, if you trade with a broker which offers you a binary options app. Most brokers have their own individually tailored apps for their own trading products, so you have to search for a broker that supports mobile trading. Not all binary options websites currently offer mobile support since this is an emerging market. Developing a mobile app does take some work, since the app ... If you want to trade at any time and any location you need a binary options app on your mobile phone or tablet. When trading in very short term expiration periods, being able to make the trade at the right time is paramount. Brokers recognise this, and of course, they want their clients to be able to trade wherever, and whenever they choose to. So trading via a mobile app is a key offering for ... We sent our binary options and technology experts to explore the various trading apps offered by the various binary options brokers available in the industry. The experts would explore the various apps offered and how much tools and resources are on the apps. IQ Option emerged to be the binary options broker with the best binary option trading app. Below, we explore some of the reasons that ... A binary trading app with a demo account can be a great way of putting it to the test. At the very least, you ought to be able to access this without providing any bank card details (and ideally, without your email address or other personal info). IQ option provides this functionality with its mobile app. A Practice App. A decent demo account app also performs another useful role; it doubles ... If you have an Android phone, you can only download Android apps. The same applies to Apple users and iOS apps. When a binary-options broker offers multiple trading applications, it gives users more flexibility, allowing them to find the right app for their phone. The United States has the most smartphone users of any country at 260 million ...

    [index] [3190] [25162] [3062] [1861] [9064] [21733] [9895] [9598] [14038] [1910]

    How to install IQ Option app on android and iOS - Binary ...

    60 Seconds Binary Options Trading with Lbinary's Android app - Duration: 3:38. LBinary Options 12,411 views. 3:38. Binary Options - When to Enter Trades - Duration: 7:44. ... IQ Copy Trading Platform 2020 Fully Automated trading Robot for I Q Option BinaryDigitalCrypto - Duration: 21:38. IQ Copy Trading - Fully Automated Trading Robot 7,922 views 21:38 IQ Options -https://affiliate.iqoption.com/redir/...Please subscribe and leave a like for more videos.Online trading is a very risky investment/profession. It i... binary options strategy, binary options uk, binary agency, options army, binary best, binary indicator, options robot, binary scams, iq options https://binaryoptionsbeat.com/ #Binaryoptions #Nadex #Nadextutorial You can always contact me via [email protected] In this video I tried to explain ... binary options team alliance teamalliance binary.com binary trading binary iq option options trading expert option stock trade day trading analysis iqoption finance profit wall street bitcoin ... How to Use MetaTrader 4 - an Introduction for Binary Options Trader. https://goo.gl/2zlDqi MetaTrader4 – The MUST have Charting Software Before you start...

    http://binary-optiontrade.studecefexka.tk