Damn web designers and their vertical lines -_-
seen from Malaysia
seen from United States
seen from Guatemala

seen from Malaysia
seen from China
seen from Russia
seen from United States

seen from United States
seen from United States
seen from Japan
seen from Chile

seen from Malaysia
seen from Mozambique

seen from Canada

seen from United States

seen from Malaysia
seen from Singapore
seen from United States
seen from United States

seen from Russia
Damn web designers and their vertical lines -_-
vieralynn replied to your post“Me: Spends 2 hours researching bug only to realise I can’t reproduce...”
Tbh, web programming is a special kind of hell that combines every worst case scenario imaginable.
I'm glad you say that. There's a lot of stuff to learn.
That being said, what bothers me about this particular scenario is I thought I'd checked everything. Client side web stuff can be such a pain to me because I'm not as familiar with the different tools and ways of debugging to find errors as I am with C# in Visual Studio. (Oh how I love those IDE tools. I don't think I'd be a programmer without them.) I thought I would remember to check the browser console for errors.
I'd forgotten. -_- Error message was loud and clear: '403 error' (or what it said).
Back to the drawing board. Back to learning. Back to gaining micro chips of experience to perhaps one day be a proper programmer.
Me: Spends 2 hours researching bug only to realise I can't reproduce it locally, on production server it only faults in certain browsers, concluding that 'this form isn't returning shit to our code and I have no idea why' Coworker: Spots within 3 second that external service isn't returning form results in Firefox + Chrome because of their new HTTPS policy
Me: -_-
[11:06:45] Fangu: I also want to write something similar that avoids programming stereotypes
[11:06:51] Fangu: 'slaying a dragon' is... eh.
[11:07:36] Fangu: how about 'you threw too many rocks at the kid who bullied you, he died'
[11:07:51] Fangu: or 'that rock was too heavy, he died'
[11:08:12] Fangu: find the right amount of weighty rocks to knock a bullying kid unconscious
[11:08:23] Fangu: or a cat-caller
[11:08:26] Fangu: now we talkin
Srsly, Safari is taken over IE's role of that one bitch browser who needs special treatment -_-
So I got stuck fiddling with stupid jQuery/JavaScript for my blog. I realized it was time to stop when I kept staring at code using Date.GetDate() and couldn't for the life of me figure out why it didn't work - so I had to call in my boyfriend for 'blind assistance' and indeed, it's supposed to be Date.getDate(). Small g in get. Duh.
So. As the bit below the date of this post will say: Fangu wrote this while she was supposed to be sleeping.
vieralynn replied to your post:Ugh I really should clean up the JavaScript/jQuery...
no php. nooooooooo php.
XD Indeed. Indeed.
C#. Used to it now. C# and a handful of carefully picked client side languages. And some very very strict layer towards the DB.
Ugh I still have so much to learn. HTTP, SSL, caching, cookies, sessions... source control, deployment. So much to learn. About how they really work.
The stuff I'm doing at work right now is kind of like being in the Matrix, realising there are no limits, no borders, everything is just one big clusterfuck of ones and zeros and I'm not there yet where I see the big picture.
All this time I've clung to the concept of 'physical objects', because that's what object oriented programming teaches you (and it's a very clever way to make programming concepts understandable to humans), but in the end, a page isn't a page, it's output information that software such as a web browser, interprets as a page. Which completely makes sense, but still is hard wrapping your head around when things get complex.
The way I'm using server software/ code and client side code at the moment, the borders between these concepts are blurred - I've always anchored to the thought that rendering a Page from the server (with all the headers and whatnot) is the 'main request', and then you can repopulate parts of that page with AJAX etc. But the way this script works is, it caches/loads stuff so that when you scroll (= triggering JS/jQuery/AJAX), the browser changes the headers of the page (changing the url; it's a thing made for search engines) so if you're viewing the source code, the 'Page' have changed - and I'll need time to anchor what all that really means.
...I have SO far to go. -_-