Have you tried turning it off and on again?

[Kidding] - that sucks, hope things come right for you 👌

@RogueScholar unfortunately I code better than I sing (and don't know how I fixed the bug) 😅

@SomeNone no smart as in 'smart' home / phone. Turns out it means the customer wants a full line item sales export for the last 6 months 🤷‍♂️

MVP stands for "minimum viable product" - it's not an architecture, it's a business term to describe a beta version of a new thing.

You dodged more bullets that Neo there...

He probably had to fix a printer

Source? Just surprised to see a south african tech meme. (Sabc1 is a state owned news channel)

Poor Bobby DROP TABLE...

He wanted to make sure if he got the job that you were always aware he would like A RAISE

@heyheni yeah but I'm planning on keeping it small though like never larger than a single team. I'm actually about to outsource a bunch of rest apis to a dev friend so that I can tackle some higher paying low level services.

http://doxsey.net/blog/...

Thank me later

Lol even UX has anti patterns!

@seraphimsystems Joy's of working with undocumented API's 🤣

@Fast-Nop alot of IE6's issues and behaviour persisted in IE7, mostly for Microsofts own backwards compatibility.

A few IE6 critical issues were addressed and standardised and then in true IE style they promptly filled the gaps with some new shiny non standardized IE7 behaviour. Much more subtle but the same issues in different places... at one stage we had individual style sheets for ie 6-8.

People were pissed, Microsoft took notice and were losing browser market share rapidly so they finally agreed to follow the w3 specifications more closely and stopped trying to reinvent and force their idea of the web on the world.

Hence from IE8 on cross browser development became far easier and rendering consistently got better.

@simpleJack The vast majority of web devs globally have less than 5 years experience so they skipped the dark ages or were juniors in IE6 's final days and weren't directly responsible for making the sites cross browser compatible.

IE6 is like a GOTO statement - so notorious that everyone knows it is bad but far less can actually tell you why it is bad.

Even if you had the unfortunate experience of having to deal with IE6 enough to realise it was fucked if you weren't directly responsible for porting 2000 lines of CSS to a 8000 line IE specific style sheet you got off easy

@gitpush good point! That makes me feel a bit better...

@n3xus that's cheap! Fuel in south Africa is around $1,50 cad/litre 😬... how much is it for a second hand car, nothing fancy 100k+ on the clock?

Oh and how are your food prices? Buying takeout vs cooking a meal would be a good measure.

You guys are helping alot... so far it looks like your getting a new neighbor' 🤘

@ewpratten thanks giving me some places start... honestly Ontario has a strong selling point just being close enough to check out your robotics competitions!

@n3xus Thanks alot for the advise!

I've already been warned on the dental - current advise is to rather plan a holiday back to your birth country and visit the dentist while your there lol.

Did you immigrate to Canada?... any hidden costs/ surprises to watch out for?

In terms of province / location do you or @ewpratten have any recommendations on where work/live?

@ewpratten awesome I never realised you were Canadian! Thanks man

*EXCEPT WHEN HOTFIXING PRODUCTION*

@linuxxx I'm referring to the amount of meta data leaking out and lying around the web of devices you need to use to be part of society. When you realise the state and extent of web security you realise its only something we are starting to fix now. Everyone's already been pwned atleast once

@linuxxx because devs cant tell which information is important

@gitpush we all should be lol - if devrant had a little more money to throw at storage and wasn't so heavy on image compression the workspace reveal might have in advertly become one massive chain of data breaches

@gitpush no ‐ Thank you for posting the rant I enjoyed it, I love playing with xss attached attacks in the wild (purely from a secops perspective).

My point is about second questioning all the meta data we consider harmless or meaningless - in our applications and personal lives that we either dont think is worth stealing or securing.

I thought your pic was obscured beyond recognition - 99% of would, especially since the info is so 'generic', but that does not equate to uniqueness. Now consider that It took me 2 Google queries to get a screenshot that was intentionally obscured as the top result (first one returned the theme) - just how much personally identifiable meta data packets are lying around or embedded in a high res selfie

@tokumei look at screen shot - @gitpush intentionally obscured it to prevent misuse. Then click the link and find the site on the top Google result

The matrix.org hack - https://devrant.com/rants/2062377/...

@linux

@gitpush

@2erXre5 I ran an obscured version, probably the exact same file I used to prank co-workers. My default obscufication method which apart from making it fuck hard to read added sugar to delete itself while it runs in memory (occasionally I would add bits of code to remove log files or worse add fake entries to fuck with people ).

I'm sure I have the source somewhere but it's on one 12 loose hard disks in my cupboard.

You can mostly replicate it in a line or 2, just wget a midi of the clicking and loop it in the background ( change the volume to a fixed level each loop to make them doubt it's their speakers ). That's enough to make anyone IT panic.

My advise would be not to write code, well at least not until it's a last resort.

Live coding is pretty similar to whiteboarding in the terms that it exists to test your problem solving ability and coding habits / style not your ability to memorize arbitrary syntax. So when I interview and ask a dev to write some code it's more about checking that he can work through and solve problems without help, has some kind of coding / indentation standards and doesn't name variable "x" or "foo".

My advise is

1. When speaking, talk them through your thinking as if it's a dev coming to you for help.

2. Talk through the problem first and mention any potential caveats or upsides of possible approaches. Pick the simplest approach in terms of time and loc that will work. If it's a little sketchy or won't scale make it known and explain that you have chosen your approach for time constraints / demo purposes move on and solve the initial problem you were asked. Unless you were asked to write scalable code or a solution with 0(1) it's not part of the problem.

3. Walk through the problem again, this time adding comments or pseudo code for each step needed to solve it.

4. Finally write the code. At this point they already know if your a good candidate and your in as long as your code style doesnt make them cringe - focus on structure and clean variable names. If you can't remember the exact syntax to map an array or split a string usually no one cares because it's obvious that you know the data type and it's common methods and your interviewer will usually help you along.

Most candidates I hire don't get far enough to compile / test the code because I already know are skilled enough between 2 & 3 so I stop them after writing a few lines and move on.
Most who do finish coding I don't hire because I was either curious if their crap would actually compile or they took far too long and I didn't want to demoralize and stop them.

@TrojanMorse it's the latest stupid fad on Facebook- people post pics of themselves 10 years ago vs now