Hey folks! As you may have seen on meta, at the community's request, the site name has been changed to Psychology & Neuroscience Stack Exchange. If you see any bits or bobs we overlooked, let me know!
We made it, y'all! We just pushed the changes and now, after 8 long months...
The name for the site has changed to Software Engineering Stack Exchange.
The logo for the site has been updated to the one shown in the top left of the page.
The default domain for the site has changed to softwareeng...
@enderland actually, if it's all the same to you, I'll edit the title of your post so that it's a little clearer what's being celebrated, and drop an answer as official confirmation that yes, the name change is complete!
ya know I've been thinking on this, and I'm pretty excited about this direction for you all (yes, I know it's an articulation of that which has already taking place, but bare with me). there are more new developers than ever, more new frameworks and libraries being pushed at them from every direction, and almost no one anywhere to advise them on the craftsmenship of software
Reminds me...gnat's meta post about what should be done when debugging questions inevitably do show up was a little premature, but it's still the right conversation.
I mean, I'm speaking purely for myself, as an actual novice programmer. And hopefully there are at least a few others out there who could be trusted to pick up on the same sensibilities when faced with that list.
As a novice programmer who wants to be a good programmer, if I show up here and read that, I know from those 4 bullets exactly what I should and shouldn't ask.
> On topic - development methods and practices - requirements, architecture, and design - quality assurance and testing - configuration, build and release management
> On topic - development methods and practices - software requirements, architecture, and design - quality assurance and testing - configuration, build and release management
@maple_shaft Given that algorithms are something software engineers may employ to implement a design, doesn't it stand to reason that the folks you want participating would be able to deduce that themselves?
> On topic - software requirements, architecture, and design - algorithms and data structures - quality assurance and testing - configuration, build and release management
Off topic - troubleshooting or debugging code - requests for code - what to read, learn, buy or use. - legal advice
Ah, yeah. Overlap with PM.SE is something I want to think about a bit more actually...but one thing at a time. I see what you mean about 'process and methods', and why leaving that out might be riding the line in failing to convey the site's purpose.
Cool. I recognize that this was a sticky one when we last brought it up, though I've continued to be rather partial to the proposal Shog laid out here because it seems to communicate the most impactful information most quickly.
Honestly I recommend we stick with the tagline we have. Mention of the SDLC is the one thing, in our long, laborious conversations that got us on the same page. It's not perfect, it will not encapsulate everything while rooting around all edge cases, but it gets us most of the way there and provides clarity for most of the people whom you want to attract.
Today, I'd like get back to figuring out the bullets for /on-topic and just generally make sure we keep being on the same page. Anything you all want to bring up after this past month's conversations?
Been following meta conversations closely since we last spoke, and I think the community's been surfacing a lot of the right questions. Honestly, it's been great to see folks getting involved. When we last spoke, we came to consensus on why we're doing any of this in the first place, and then got clear on the new site name and tagline, represented here:
...And it looks like it might be a little late in the day for folks. @ThomasOwens ping us when you're around again and we'll pick up where we left off last Friday.