Edit - Software Engineering Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

Rev

4

I didn't think SQL was Turing-complete, unless you're talking about T-SQL or PL/SQL.

FrustratedWithFormsDesigner
– FrustratedWithFormsDesigner

2011-02-23 18:36:11 +00:00
Commented Feb 23, 2011 at 18:36
@FrustratedWithFormsDesigner: You're right! Thanks for picking me up on that. (However, the point I'm making stands - that declarative languages can be T-C)

Kramii
– Kramii

2011-03-03 10:41:58 +00:00
Commented Mar 3, 2011 at 10:41
1

Very good answers. As a web-developer I've seen over-and-over again situations where clients' are impressed far more with a "flashy" design than by proposed functionality. Whilst this may offend our purist programmer instincts (that functionality should be king) it is something we ignore at our peril.

Dan Diplo
– Dan Diplo

2011-08-12 07:59:14 +00:00
Commented Aug 12, 2011 at 7:59
5

+1: Joel Spolsky has an interesting blog post that takes up the problem with function vs flashy GUI. Especially the hazards of showing a 100% finished and very flashy GUI when the functionality is not in place. A good read if you havent read it. joelonsoftware.com/articles/fog0000000356.html

Leo
– Leo

2013-01-25 08:21:43 +00:00
Commented Jan 25, 2013 at 8:21
3

"They might well be more productive with feel-good tools than with technically superior tools" - True, true, true! Apple has built their business on this. Don't get me wrong, Mac has substance too, but what has made some people pay almost twice as much for a Mac machine as a Linux or Windows one is that it looks cool and it feels good to use.

GlenPeterson
– GlenPeterson

2013-06-06 14:20:00 +00:00
Commented Jun 6, 2013 at 14:20

| Show 2 more comments

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »