FAILED_DOCUMENT_REQUEST. Timed - out - wordpress

my WordPress site for FAILED_DOCUMENT_REQUEST. Timed - out suddenly, what to do now? I m a newbie in coding......suddenly, what to do now?
Thank you all for your kind help!

Just to close the question, i have settled this by SHOPIFY.
Yar dun try using tech stuff too much time if u are not a tech nerd but trying to learn. Its meaning...less, anyways SHOPIFY handled that.
one more thing in the world I know from the pandemic.
dun believe in self learn mysteries , for those un tech new bies, I m also,
just try to get money solve the problems, nobody have the time to help u out even they are seems nice kind tech ppl becox they are busy earning money.
So finally solution - > difficult tech problem, -> shopify(money) ->earn money.

Related

default start reputaion at stackoverflow for new users?

i want to know what is the default start reputaion at stackoverflow for new users?
BTW i studied informatics and recievied an excelent diploma (needs only 3 years for it) but i disagreed with some here. they downvoted me.
sad. seems not a fair place here for beginner. not tolorant place for new users with unusual answers. and they gave me not the chance to answer - often (becouse topic fast closed they technically restricted me). so my conclusion: not a fair place for new users and you dont get normal users by waiting. and if you work or develop at isolated section of programming the meanstrem people her downgrad you fast with now chance justify/explain for you. good place for collect answer. bad place to start helping people. thats was my feedback (or may a goodbye) from a new and frustrated users with informatics diploma.

Projects made with a CMS -> Money problems

i want to discuss about a problem: i've lately had discussions with some customers to which i've asked money for projects written in Drupal: when they know that i use a CMS they immediately say that they want to pay less "because I use a CMS".
I develope since 15 years and i've made many many projects without using a CMS and by using my libraries; i'm lately using a CMS but this does not mean that i don't write code ...
Which could be the best response to give to a similar question?
Ciao
c.
Explain it to them very simply.
If you have to install and configure any Content Management System, that takes you more time and therefore costs a bit more than a static website. You need be as transparent as possible when you detail the costs, so tell them how much time will be spend designing the theme, how much time will be spend configuring Drupal for their website and so on.
It would be interesting to ask them why they think it should be cheaper, as you will then understand what misconception they have about CMS. You can then explain things better to them so that they understand what using a CMS actually means.
I would say that they are paying for your expertise and experience, regardless of the tools you use. If they want it cheaper, they can ask someone else. The CMS helps to add stability, security and expandability to what they would get if they had a custom solution.
Plus, if it was all custom code it would be extremely difficult to hire someone else to take over if, God forbid, you were hit by a bus. The CMS gives THEM more options.
I would agree that you should explain where the money is going, in general terms, but you shouldn't have to justify every detail. Otherwise how do you itemize "dealing with stupid customers who need their password reset for the millionth time" or "explaining the difference between a 100x100 thumbnail JPG and a 3600x2700 BMP". It could also open the door to a lot of haggling that will just waste your time and frustrate you.
I had a client who asked me over and over again the same kind of question.
If your client doesn't perceive the value you're adding to an Open Source application then give them the source code and point them to the documentation. Tell them to build it themselves.

used biocep with AWS?

Has anyone used biocep with AWS? I see a lot of presentations online but nothing that seems to do a thorough job of walking you through the process. There seems to be a lot of complexity to get your head around. I was hoping someone could point me to particularly useful forum threads or [even better] some real tutorials?
Having just heard the author speak at useR2010, I believe that project is dead or has at least morphed into something else.

How much Work-power and time does it take for building website like stackoverflow?

I'm wondering building a website like StackOverFlow (approximately the same features using ASP.NET ) How much Work-power and time does it take in your opinion .
My boss has asked me to estimate for work-power , time , cost and suitable technologies .
I appreciate any direction .
I believe that the site would take plenty of time to implement. If I'd have to pull a guess of thin air I'd say somewhere between 800-1200 man hours.
Then comes the setting up servers, ensuring scalability, testing, fine-tuning algorithms.
So depending on how good you or your team is it could take anywhere up to a year to write something like this.
Disclaimer: I am just talking based on 10 years of experience with web-development. But I could be COMPLETELY wrong.
Buddy, there is a website similar to this called http://startups.com
You can probably ask this question there. Its specifically designed to answer questions like this. Whereas stackoverflow is intended for programmers and programming related questions. I see this question being asked here a bit isolated.
People come to this site and think wow stackoverflow this is an easy site to create.
I mean all it is is post a question then people submit an answer. I think that is a big misconception. Maybe just maybe the database is quite simple, a question has multiple answers and an answer has multiple comments associate with it. If you dig deep into it the questions and answers could actually be stored in the same table...with some indicator as to whether it is a question or an answer. But to answer your question, I don't think it is as simple as one might think. It's definitely not difficult in the logical sense (it's doable). What I am saying is it is more then a one week job :).
it is not that hard to do the site. the design is nice but simple. the engine isint THAT complicated (or so it looks). biggest problem is the load that falls on this site and the hard task of moderating/maintaining it. and the best part of it is the idea ;)
I think that the diffuclt of stackoverflow is to get community (very good quality community, not like yahoo answers).
Not only that, also use cases from stack overflow are pretty cool and adapt very well to get a good community.
About work-power a good skilled programmer could start it, if at full time like a month or less could do it. BUT! the programmer should have the idea,not a freelance or something like that, freelance or slave monkey coder could take a more time to do it.
But there are more problems, like money to invest at very begin of the app for example in hosting / server power costs.
Also stack overflow, could be compared to forums...its like a forum evoled or something similar.
Someone said that requires a lot of work power, I disagree if you start something to get the best scability,etcs (like project of big scale) you are going to death of that project.
Start something simple, very simple when there are scability problems start with that but no at begin!
Probably longer than you expect:
Code: It's Trivial (by Jeff Atwood)

How do you learn a new skill/framework/technology?

I need to be able to contribute to a relatively large Adobe AIR project and I'm starting from scratch with this technology. What's the best way to go about it?
I usually get a good book/tutorial and work my way through it but this time it seems there's just too much to learn for this to be feasible within a reasonable time frame. I would need books on Actionscript, FLEX, etc...
Do you know of any good resources that might be useful for this particular case?
How would you go about it if you were in my shoes?
I just had to do something similar. If you can afford it (or, get your company to pay for it), try doing a training class. I did one by Figleaf software a couple months ago and it really helped.
As for books, I hear the Essential Actionscript 3 book is good (I have the one for AS2 and it's quite good). Flex is really just the SDK. You'll be doing most of your work in AS3 and MXML.
Another really good thing to do is download the SDK and start playing with it. Think of a couple small apps to do, then write them in Flex. I did this at work (wrote a couple util Apps in Flex to learn it). I find the best way to learn is to do it, and the SDK is free so there shouldn't be anything stopping you.
Hello World for AIR, then progressively add detail.
Aggressively use any communities out there.
Blog about your experience. One day you will help someone else.
Today you are learning, tomorrow you are teaching.
I download samples from the Internet, and run them, mess with them, try to change them and understand how they work.
I subscribe to blogs on the topic and do samples, try to understan the stuff people write about.
And I do samples :)
So I basically learn from the top - down. First I get the general sense of the technology, and then I drill down with the samples to the parts that I find interesting. Works pretty well. :)
I usually find online tutorials are the best way to go. They are more to the point than books, so it's usually quicker to get up to speed. And don't limit yourself to a single resource. I've never had problems finding enough tutorials through our friend google.
I have no knowledge about Adobe AIR though. I assume your customer knows you're a noob too? ;D
I'm a big advocate of active learning, which is described in detail, here. Essentially, when you are trying to learn a new technology: read about it, discuss it with your peers, teach it to people who are even newer to the technology, and most importantly, get your hands dirty.
A perfect example of how you can learn new things is by getting involved with a community such as stackoverflow, or a discussion forum based around what you would like to learn (http://www.adobe.com/devnet/air/), or even by contributing to an open-source project.
Of course, none of the above is as effective as trying new things out. In order to learn new technologies (in my honest opinon), it is best to dive in "head-first" and try things out.

Resources