Timeline for Follow-Up 2: New Site Name and Scope Proposals
Current License: CC BY-SA 3.0
8 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Mar 16, 2017 at 17:21 | history | edited | CommunityBot |
replaced http://meta.programmers.stackexchange.com/ with https://softwareengineering.meta.stackexchange.com/
|
|
Aug 31, 2016 at 22:15 | comment | added | Jerry101 | Aha! Indeed, your point is key to this renaming project. The name and description need to work not just for people "inside the tent" but also for people in nearby "tents". How to fix that? How to distinguish between programming per se (SO), theory (CS), and the practical issues that arise at production scale, when building s/w for many users, safety critical or money critical s/w; building with success criteria, teamwork, schedules, etc.? That's when we need principles to engineer a success. [I'm listing key terms here in hopes of triggering ideas.] | |
Aug 31, 2016 at 19:07 | comment | added | ricksmt | If off-topic questions is really what's driving this name change, then we ought to pick our new name with the users who create those poor questions in mind. I think the new name is clear only to a subset of our own membership, and certainly not those who we're trying to target. | |
Aug 31, 2016 at 19:06 | comment | added | ricksmt | @Jerry101 I now understand the distinction you are going for. I still think this new name does not convey the distinction you want to make, at least not to the majority of people. I don't think this will separate the theory from the practice for the average user. Even after it's been made clear to me, my primary association is to the working field. | |
Aug 31, 2016 at 16:52 | comment | added | Jerry101 | We're struggling to usefully distinguish this site from others (so people can participate as they want) and to convey that even if it's fuzzy & subtle as you noted. "Software Engineering" is about applying engineering principles to software development (softwareengineerinsider.com/articles/…) vs. the s/w development part per se and everything else software engineers discuss. It's like the distinctions between automotive engineering, building cars, and auto engineers. en.wikipedia.org/wiki/Automotive_engineering | |
Aug 31, 2016 at 15:40 | comment | added | ricksmt | @Jerry101 I fail to see your point. The term engineering does not exclude the construction or the means of doing it. (I don't understand how stock options got included.) Software engineering covers a larger scope than what the fine print of these discussions indicates the scope of this site is. Correcting me about what the scope actually is does not change what the perceived scope will be. | |
Aug 31, 2016 at 5:17 | comment | added | Jerry101 | The proposed name is "Software Engineering", not "Software Engineers". So the scope includes ways to engineer software, that is, principles to reliably achieve qualities like safety and usefulness, but not other questions that engineers have such as about favorite tools, software heroes, and stock options. | |
Aug 30, 2016 at 21:22 | history | answered | ricksmt | CC BY-SA 3.0 |