The best test I’ve ever seen!!
describe('The component renders ok', () => {
it('renders without error', () => {
expect(true).toBeTruthy()
})
})
And there it is… the best test ever written!
I laughed.
We write things we think about
describe('The component renders ok', () => {
it('renders without error', () => {
expect(true).toBeTruthy()
})
})
And there it is… the best test ever written!
I laughed.
In every interview curcit I find myself having to explain what a closure is to people. With it being such a simple thing yet misunderstood I realised today that I should really just have it summed up in one sentence rather than having to bumble through and then in the end just say oh… can I just show you.
A closure is a JavaScript function’s ability to access/remember variables within its local scope after execution.
Hopefully this will stop me looking like a excited teenager eager to learn while staring into my knowledgeable interviewer’s eyes and morph me into the somewhat knowledgeable employable keen JS dev I am.
One thing to watch out for though, is JS by keeping these closures open will not garbage dump inside these functions as they need to keep the variables alive. I haven’t seen this causing me any real problems but performance will be an issue.
I’ve had Virgin Media or rather Telewest (Blueyonder as the internet part of their company was called) since they first introduced 512kbs broadband. to the UK in, I am guessing but I was in year 6 at Fortismere, so i believe 2001 or 2002. I clearly remember talking to Alex Tenyson about it and that I would be able to download the lord of the rings films from Kazza in 350seconds. He pointed out I wouldn’t actually get a download of that speed 🙁 More like 50kps download. I’d ben trying to download the liveCD’s of the film, 3 discs all on dial up 🙂
http://news.bbc.co.uk/1/hi/business/687899.stm
Since then, its been consistently upgraded and now I sit on a 300mbs connection, which yields a weak 60mbps and a 12mbps upload. I must say, I’ve seemingly always been disappointed with virgins service. I’ve had it every house I’ve been in and never ever once got the full speed I was paying for. They have offered me a constant £9 reduction on my bill, which still comes out at £118 a month. Ok, I have Sky Sports on that. But still, its not good enough. In my last property which I was there for 4 years, we had 6 visits from a engineer, here I haven’t even bothered. I got the discount and there were problems in our area
which were to last 2 years apparently. Anyway, its over now… I hope.
I didn’t think this was a problem until I found out about https://www.hyperoptic.com/. I don’t remember where I first heard about these guys, but in Febuary 2016 I found their site and signed up my interest, I then started to talk to my near by friends (neighbours) and told them to register their interest as well. Now some 16 months later today it gets installed!! 1gb internet up and down! lol I’m excited! Very excited!
I will return with a speed test soon lol
I’ve been away for node for well what seems like forever, but its maybe been 6 months since I did it at work and 13 months since I did it at home… A long time.
I’ve spent this evening bringing the new Norseman Old Mayfield site that I had been working on before the fall (of mayfield)
Its a promise hell in this project so I thought, urgh somebody must have done something cool by now, google it bosh:
https://mattdesl.svbtle.com/debugging-nodejs-in-chrome-devtools
Fantastic!!!!
Now I can interact with my objects and what not in the f’in mother fudging CONSOLE! hahah yes!
But mainly… its the one file thing, its driving me nuts how brilliant this. I thought requireJS was half decent. Now I realise that it was convoluted and bloody confusing at times
Being able to just use requires is really refreshing…
(function e(t,n,r){function s(o,u){if(!n[o]){if(!t[o]){var a=typeof require=="function"&&require;if(!u&&a)return a(o,!0);if(i)return i(o,!0);var f=new Error("Cannot find module '"+o+"'");throw f.code="MODULE_NOT_FOUND",f}var l=n[o]={exports:{}};t[o][0].call(l.exports,function(e){var n=t[o][1][e];return s(n?n:e)},l,l.exports,e,t,n,r)}return n[o].exports}var i=typeof require=="function"&&require;for(var o=0;o<r.length;o++)s(r[o]);return s})({1:[function(require,module,exports){ /** * Created by Hutber on 10/12/2014. */ 'use strict'; //require('./templates'); require('./core');
Etc
It seems to me that the name choice for the new App Sex Diaries which lets its users track their sex and get naughty little graphs and what not was a bad name choice in hindsight.
Anything with Sex in it is a rather hot keyword. Much to my shame.
The key to success? Change my name and make sure people know that Sex Diaries is a Sex Tracker and not just some diary that does nothing.
Alas, we won’t change the name but I will try and make sure people know that Sex Diaries is a Sex Tracker which is no easy task.
Blogging about it… If you’ve got one blog about it as well 😀
So, after much up and downing with my emotions the app is now currently living: https://play.google.com/store/apps/details?id=co.uk.couplesdiaries
Brilliant. This makes me very happy, shame though that I can no longer manage the app.
The app is still 0.0.1 so very far from being finished, but its still time to get the social side of things going.
So, Step 4. Well I’ve started some adverts, thanks Ryan. But I still think that 82 Likes, it just doesn’t look that sexy you know?
Que: https://boostlikes.com/ These guys, offer some very very cheap booster likes. I do believe that I will be going for the Web Page Likes, $22 for 500 likes. If I can get 500 people looking at my site I’ll be a happy man 🙂
[Edit]
I’d just like to take the time to give you a summary of why I feel this process is broken, as other have pointed out, they feel this app does in fact breach Google’s policy. Now I accept that this app may indeed deserve being pulled from the store, however this is opinon based, but at the end of the day this is Googles call to make. My only problem with the way it is currently working is the lack of clarity offered, the non specific section that my app is failing at.
In other words, please tell me which images are the problem and I can change them, instantly, within minutes I could have a new version online. For the time I have spent this would be a pleasure.
A new developer has now taken over the development of sex diaries.
Original
I’ve been developing sex diaries now for well over a year. The last 5 months day and night almost solidly. The last 2 weeks have been just bug fixing and tightening this little bad boy up to be usable.
So next time, get some beta testers. So I signed up for a developers account and built a release version to upload. All very exciting.
I downloaded it directly from the store. That was nice..
This is a notification that your application, Sex Diaries Alpha, with package ID co.uk.sexdiaries.app, has been removed from the Google Play Store.
REASON FOR REMOVAL: Violation of the sexually explicit material provision of the Content Policy:
- Apps that contain or promote pornography are prohibited; this includes sexually-explicit or erotic content, icons, titles, or descriptions.
Please refer to the Sex and Nudity policy help article for more information.
All violations are tracked. Serious or repeated violations of any nature will result in the termination of your developer account, and investigation and possible termination of related Google accounts. If your account is terminated, payments will cease and Google may recover the proceeds of any past sales and/or the cost of any associated fees (such as chargebacks and transaction fees) from you. If your developer account is still in good standing, you may revise and upload a policy compliant version of your application as a new package name. Before uploading any new applications, please review the Developer Distribution Agreement and Content Policy.
The Google Play Team
A bit of a shock but at the same time kind of understandable. Looking up in the policy
Sex and Nudity
Google Play is not for pornography or sexually explicit content, and most nudity is not allowed. As a rule of thumb, if content is intended to be sexually gratifying, it is not acceptable on Play. Content which promotes incest or bestiality is forbidden.
The only thing that stood out for me was the fact that bestiality is not allowed. So, Donkey + Sex might not be that cool.
I found the lack of information about why the app had been suspended very ambiguous. Its open to interpretation. So for me, change the things that I think are wrong and reupload as my account is still in googe standing.
So the next day I changed what I thought was the problem and reuploaded with a different app name:
More testing more fixing but also waiting for the email to tell me I’d be naughty.
This is a notification that your application, Sex Diaries Beta, with package ID co.uk.sexdiariesalpha.app, has been removed from the Google Play Store.
REASON FOR REMOVAL: Violation of the sexually explicit material provision of the Content Policy.
After a regular review, we have determined that your app contains images of illustrated nudity. This violates the Content Policy. Please refer to the Sex and Nudity policy help article for more information.
All violations are tracked. Serious or repeated violations of any nature will result in the termination of your developer account, and investigation and possible termination of related Google accounts. If your account is terminated, payments will cease and Google may recover the proceeds of any past sales and/or the cost of any associated fees (such as chargebacks and transaction fees) from you.
If your developer account is still in good standing, you may revise and upload a new instance of the app that is compliant with the developer terms. Before uploading any new applications, please review the Developer Distribution Agreement and Content Policy.
If you feel we have made this determination in error, you can visit this Google Play Help Center article for additional information regarding this removal.
The Google Play Team
However this time with a good slightly more detailed message
we have determined that your app contains images of illustrated nudity
I thought at this point it was worth a little appeal on 2 basis’s. I’ve changed images making it a lot less ‘Sexual’ in my opinion but also looking into the app store, doing a simple search in the play store brings 100’s of app’s with actually sexual content and well sleazy. That’s a huge frustration.
The Appeal
Thank you for flagging this app as Sexually explicit
material as I am a strong believer that anything that might be pornographic
or sexually explicit should not be allowed on the Play store.I do feel however that in this particular case that no nudity nor sexually
explicit content has been added that has not already been seen on the app.There are 9 illustrations in the app, of which 5 are used. I believe only
one of the images depicts sex. Without any genitalia on show.I have looked at other similar apps:
https://play.google.com/store/apps/details?id=com.androcn.brjn.lovcal
https://play.google.com/store/apps/details?id=com.xiaobin.oldtempThe above apps do how other images in a similar style. This however does
not and should not effect mine. I am just curious if at all possible, if I
could get some more detailed information so that I might change the
graphics to be safe for the Play Store.Any more information would be gratefully received.
Thanks You
Jamie
The reply
Hi,
We have reviewed your appeal and will not be reinstating your app. This decision is final and we will not be responding to any additional emails regarding this removal.
As you may be aware, we do not pre-screen applications submitted to the Google Play. If you would like to report an app that you believe is a violation of the developer terms please flag it as inappropriate via the Google Play app or submit a report through our contact form.
Be advised that any perceived compliance or non-compliance of other developers’ apps has no bearing on the compliance of your own apps.
If your account is still in good standing and the nature of your app allows for republishing you may consider releasing a new, policy compliant version of your app to Google Play under a new package name. We are unable to comment further on the specific policy basis for this removal or provide guidance on bringing future versions of your app into policy compliance. Instead, please reference the REASON FOR REMOVAL in the initial notification email from Google Play.
Please note that additional violations may result in a suspension of your Google Play Developer account.
Regards,
The Google Play Team
Back to the illustration board.
Changed all the things I thought were terribly naughty and reuploaded again with a different name. Uploaded with the understand that if they don’t accept it I’ll be able to change it again.
This is a notification that your application, Sex Diaries Beta, with package ID co.uk.sexdiariesone.app, has been removed from the Google Play Store.
REASON FOR REMOVAL: Violation of the sexually explicit material provision of the Content Policy.
After a regular review, we have determined that your app contains images of illustrated nudity. This violates the Content Policy. Please refer to the Sex and Nudity policy help article for more information.
All violations are tracked. Serious or repeated violations of any nature will result in the termination of your developer account, and investigation and possible termination of related Google accounts. If your account is terminated, payments will cease and Google may recover the proceeds of any past sales and/or the cost of any associated fees (such as chargebacks and transaction fees) from you.
If your developer account is still in good standing, you may revise and upload a new instance of the app that is compliant with the developer terms. Before uploading any new applications, please review the Developer Distribution Agreement and Content Policy.
If you feel we have made this determination in error, you can visit this Google Play Help Center article for additional information regarding this removal.
The Google Play Team
Account Suspension:
This is a notification that your Google Play Publisher account has been terminated.
REASON FOR TERMINATION: Multiple violations of the Content Policy and Developer Distribution Agreement as outlined in previous emails sent to the registered email address of your Publisher account.
Please note that Google Play Publisher terminations are associated with developers, and may span multiple account registrations and related Google services. If you feel we have made an error, you can visit the Google Play Help Center article for additional information regarding this termination.
Please do not attempt to register a new developer account. We will not be restoring your account at this time.
The Google Play Team
So that’s it, no more uploading, no more testing, no more working what they actually want.
This has left me very frustrated with the situation. I am now banned for life from Developing and getting an App on the Play Store. Simple things they could improve (IMO)
So, we need to get google to listen to us, small single developers. There is a petition online that if you are a developer you should sign:
Dear Google Team,
Android has given a lot of technologists and independent innovators a ray of hope. Because of its openness and wide spreadness.
But now lots of small and indie developers are being terminated in the name of policy violation even without warning! or not even a single choice is given for them to correct their mistakes.
More over there are no human beings in google to assist with developers. Only automated systems simply yell out messages on a repeated basis, without solving our problem.
Making error is a human nature we are not asking for exemption from the error. But a chance and time to correct ourselves which is very reasonable for the efforts we make and our VALUABLE TIME we invest in developing apps.
Developers are not simple programs, just to delete from the system.
Many dev’s accounts are terminated without any valid reason. People work with much hope that their project would be a successful one. But suddenly they just see the termination message to their frustration.
What we demand is a reasonable warning before account termination if the error was not corrected and definitely a human intervention to assist with developers.
Hope you understand the difficulties we face with developer relationship.
Regards
on behalf of all Developers.
They clearly sum up everything that I am struggling with.
Please google, help us out.
Update
After doing much googling and on end of similar stories I still can hardly believe that this situation could exists. I’ve delt with bad API’s before, but these are understandable. A company that’s core foundation is “Don’t be evil|” it was somewhat surprising that a independent developer like myself, and the many others, would have to struggle with a system like this. With this in mind, we need to try and raise our voices a little bit and understand why google have set it up this way. If there is logic then I can’t complain, currently as it stands I and many others are completely miffed and frustrated.
Email me:
Friend me on Facebook
https://www.facebook.com/hutber
Follow me on Twitter (I rarely use):
Sign this Petition!
Another developer banned by Google, but this guy isn’t an articulate kreten like myself:
https://medium.com/p/c62f2404f66
And another developer banned by Google:
http://andrewpearson.org/?p=681
More out of control Google banning:
https://blog.hutber.com/how-my-google-devlopers-account-got-terminated-with-no-option-to-appeal/
I thought Google was cool, but I was wrong:
Search the web and you’ll find lots of similar complaints.
http://www.furioussoftware.com/2013/10/goggle-banned-me-and-my-friends-from.html
http://www.zdnet.com/blog/violetblue/why-developers-should-worry-about-google-play/1148
I never knew!!!
To live-edit Sass files in Chrome you need to have the pre-release version of the Sass compiler, which is the only version that currently supports source map generation.
gem install sass -v ‘>=3.3.0alpha’ –pre
Once Sass is installed, start the Sass compiler to watch for changes to your Sass source files and create source map files for each generated CSS file, for example:sass –watch –sourcemap sass/styles.scss:styles.css
I’ll forget this, so I need to post it again, to remind my self (why not bookmark it (as if you could ever fine things after book marking things))
Heres the full ur: https://developers.google.com/chrome-developer-tools/docs/css-preprocessors