I have a day job. Right now, I do open source purely on the side, but if I was to get enough donations/sponsors or I got paid for doing open source work, I’d happily start doing it full-time. I do sometimes contribute to open source during my paid work, but that’s more an exception than a rule.
The NHS also offers a range of other talking therapies /counselling, e.g. counselling for depression. The waiting times here can be shorter than for CBT.
If you're in dire need for help (depends on your scores and initial phone interview), you will be seen or referred quickly (within less than a month).
Any GP will refer you. If you need help with your mental health, just ask your GP for a referral, fill out the form and you will get help. It's a great system. (Did I mention that this doesn't cost anything?)
For long-term psychotherapy, you need to go private, but in many cases, a short-term intervention (e.g. over 12 weeks) is sufficient to get you through the worst and on the right track.
I think most people who suffer from actual depression, not a just a bout of sadness need long term treatment.
The NHS is poorly provisioned in this way, sadly.
Just like a diabetic who needs insulin everyday people with serious psychological conditions need regular treatment.
I'm lucky enough to be able to afford it, I don't know how I would cope if I couldn't.
There are different variations of depressions. In particular, it differs between acute and chronic occurrence.
As far as I know, acute occurrences tend to be more intense (as experienced and reported in standardised tests) on average than chronic ones. Here, the risk of, e.g. suicide is also highest. However, long-term depression has a much more long-lasting impact on one's life, so I don't want to downplay it in any way.
Acute episodes tend to have a duration of only a few weeks or months so short-term therapy can be of great help here.
I agree that chronic depression requires long-term support. Your analogy with insulin and diabetes is excellent. And yes, the NHS falls short in this area, unfortunately. It would be great if more people could get the care they need and I hope it will become possible.
So yes, the NHS is not without its flaws. But considering the little funding it receives, it provides excellent care. It just shouldn't be so underfunded. I also think that it is also remarkably well-organised compared to other countries, e.g. Germany, where everything is much more bureaucratic and expensive. I also think it's significantly that countries with more privatised health care like the US.
Ah, thx. It seems to work on Safari for me as well. However, it doesn't seem to work for Firefox and Chrome (which I used to initially test this) using the same settings. Shouldn't the browsers all have the same font lookup behaviour given the same font-family settings?
True, I'm noticing that as well. It seems that some OS X system fonts (San Francisco?) are used for rendering in Safari by default as well as in various UI elements (Tab heading, Search bars, ...), but not in the Chrome or FF browser itself, even if you set the font family to System UI fonts.
I'm developing a programming language called Morph inspired by LISP, Smalltalk, Eiffel JavaScript, Python (and others). It's extendible, homoiconic and designed to be transpiled to other languages, so that you can build entire projects with multiple applications on separate platforms from one code base. This is then coupled with a symbolic AI engine to generate, build and deploy applications at an increasingly higher level of abstraction.
The code base (and libraries and packages) serve as a knowledge base of definitions (what things are) and procedures (what things exist). The symbolic AI engine can then take information from this (essentially code snippets) and combine them in novel ways. Example: If you know what a RESTful API is (how it is defined), what MongoDB is and which data models you want to deal with, you can generate the source code for an API handling those data models with MongoDB backend from this. Other example: If you know what requests your API supports, what the semantic data types of the objects and fields are and what a UI-based application is, then you can generate a web, mobile or desktop application from this providing a wrapper around this API.
The goal here is not to replace programmers entirely, but to alleviate the pain of having to code things up manually, especially boilerplate. Because you can deal with issues at a higher level of abstraction now, this can make programming more approachable to (so far) non-programmers.
The language itself draws some inspiration from LISP, Smalltalk, Eiffel, JavaScript and Python. I guess, SICP was a huge influence on my thinking about this problem. Compilers (in particular cross-compilers) do something similar, but otherwise code generation has come a bit out of fashion (due to the limitations arising if you don't have a Turing complete language as a base). Some people have also looked at NN for code generation, but nothing usable has come from this so far afaik.
24607 (with the cheat), 621 (without) :D
Fun evening challenge :P
function isPrime(n){
if ((n<=1) || (!n % 2)) {
return false;
}
for (var k = 3; k < Math.round(Math.sqrt(n) + 0.5); k = k+2) {
if (n % k == 0) {
return false;
}
}
return true;
}
var nSpan = $("span#n")
var yesButton = $("button#yes");
var noButton = $("button#no");
var body = $("body");
function solve(){
if (isPrime(parseInt(nSpan.innerHTML)) {
yesButton.click();
} else {
noButton.click();
}
if (body.className != "end") {
setTimeout(solve,0);
}
}
solve();
It is at the moment, but it provides the right config ;) Plus, I'm planning to expand it to provide more general document layouts, so you can create "print" documents of different kinds in HTML and simply export it.
I just needed this for myself and wanted to share it with people :)
Thank you for the useful remarks. It depends on the nature of your task, doesn't it?
In most cases, a solution relating (real-life) actors, processes and objects they handle can (and will) be described in plain text. In an Enterprise environment, this may be part of the project specification. However, the actual implementation will be specified as source code. To an extent this may even apply to purely technical projects.
In a larger team, creating this specification of a project is typically part of a project manager's job. However, in a smaller team or start-up, these roles may merge and are not as clearly defined. This is especially true, if the team is focussed on both building a product and working with (potential) customers.
And of course, it's up to you to decide whether Kozo will be useful for you once it is released. ;)
This is quite accurately describing what we're trying to do on the front-end side. :) In addition to just creating RESTful APIs and backend and persistence code, we allow you to design your UI in a GUI (or using code). Views are data-driven, so you can essentially bind data from your models using drag&drop (or in code). However, instead of just using XY positioning, we focus on relative positioning of subviews (representing lower level parts of your application) to create working, well-designed interfaces (again, based on your design settings/parameters).
That's already quite accurate. However, you can also bind against external APIs and deploy Docker applications to fill the skeleton application.
The structure can be written in a JSON or XML format or alternatively be constructed using one of our libs, which are planned to be written in D, Python, Java, Ruby, PHP and possibly/almost certainly others.
We generate client & server side code and you can get the source code out in one of the supported stacks. Alternatively, we can host for you on a scalable stack, so you wouldn't need to care about setting up your own environments. If you deploy on your own stack, you obviously can have full control, if you deploy with us, we'll provide a number of configuration options, but generally it's a compiled server app running on a auto-scaling stack.
FWIW, I think this is a really cool idea. When I was trying to imagine use cases, most of them involved a project being generated on only one stack. Mobile apps are the only exception I can think of. Do you expect that most people will only generate their project once, on a single stack?
Right now, mobile seems to be the "exception". However, when you're thinking of other, "less common" stacks, like cloud-based Desktop applications or Browser extensions, new use cases become evident.
Furthermore, we're getting more and more stacks right now, such as wearables and sooner or later AR/VR devices/platforms - hence, the need for such as cross-platform tool will certainly increase. Plus, we also make developing single stack apps easier/less painful, so even then it will (hopefully ;) ) be helpful for people.
