Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Activity for meriton‭

Type On... Excerpt Status Date
Edit Post #278194 Initial revision about 4 years ago
Answer A: Do we want a wiki (or similar) alongside Q&A?
I am not categorically opposed, but I currently don't see a use case for articles. For one, wikis already exist. What would be the benefit of hosting our own rather than participating on Wikipedia? After all, Wikipedia has a very mature software and policies for this very thing. It also has a much...
(more)
about 4 years ago
Comment Post #278189 Can you elaborate why writing a question asking for the information you want to share "can be difficult"? Off hand, I don't see the difficulty. In particular, if the information is relevant to somebody, one should be able to describe the circumstance under which it is useful, should one not?
(more)
about 4 years ago
Comment Post #277306 70GB! Good gracious! For context, the [git repository of the linux kernel](https://github.com/torvalds/linux) (30 million lines of code) with 15 years of history (950000 commits) weighs in at about 4 GB (3GB history, 1 GB checkout). Perhaps your development team could slim down its repository further...
(more)
about 4 years ago
Edit Post #277984 Initial revision over 4 years ago
Answer A: Long code lines are not wrapped
As Lundin points out, there are quite a few whitespace-sensitive programming languages out there, where automatic wrapping would change the apparent meaning of the code, such as Phython or JavaScript. In particular, wrapped lines must be properly indented in many contexts, which goes way beyond the c...
(more)
over 4 years ago
Comment Post #277531 We should be really explicit that people are expected to **search thoroughly** before asking reference questions lest we become the googling service for those too lazy to google. Just now, we had somebody inquire about how DNS works who hadn't even read the relevant Wikipedia page!
(more)
over 4 years ago
Comment Post #277962 Wikipedia has a more accurate description on [how the Domain Name System works](https://en.wikipedia.org/wiki/Domain_Name_System). In particular, that article describes how the client efficiently locates the DNS servers to talk to.
(more)
over 4 years ago
Edit Post #277478 Initial revision over 4 years ago
Answer A: Asking software architecture related questions on Software Development community
Personally, I'd say that it depends on the question. Over on that other site, this ban was instituted to avoid opinion-based questions. For instance, suppose you asked: > Is Angular a great framework? and received the following replies: > Absolutely, i really love it! > No, I hate it!...
(more)
over 4 years ago
Edit Post #277472 Post edited:
Formatting and TL;DR
over 4 years ago
Edit Post #277472 Initial revision over 4 years ago
Answer A: What are the pros and cons of a composite primary key versus a unique constraint?
Facts In relational theory, each row in a relation is uniquely identified by a primary key. That's why some purists say that every table should have a primary key. Foreign keys usually reference a primary key. In particular, if you do not specify a column when creating a foreign key, the pri...
(more)
over 4 years ago
Comment Post #277456 What do you mean with "sortability reasons"? Also, Charlie said the *combination* of both columns is unique. That doesn't imply that a single colum is unique. That is, you can't create a primary key on a single column ...
(more)
over 4 years ago
Comment Post #277430 This answer could be improved by describing just how "overflowing the parser" could give rise to a security vulnerability, and why anybody would parse strings into numbers when (in OP's words) "we're never going to need to perform any mathematical equations on the number".
(more)
over 4 years ago
Comment Post #277409 It seems weird to focus on allocation times when discussing network I/O. If we can wait millions of processor cycles for a network response, we can probably afford a couple hundred cycles to allocate on the heap.
(more)
over 4 years ago
Comment Post #277373 If you have seen that page, what is still unclear? It seems to contain all the info you are looking for?
(more)
over 4 years ago
Edit Post #277393 Post edited:
over 4 years ago
Edit Post #277393 Post edited:
over 4 years ago
Edit Post #277393 Initial revision over 4 years ago
Answer A: Would a MySQL database run more efficiently with smaller varchar lengths?
The manual writes: > In contrast to CHAR, VARCHAR values are stored as a 1-byte or 2-byte length prefix plus data. The length prefix indicates the number of bytes in the value. A column uses one length byte if values require no more than 255 bytes, two length bytes if values may require more than ...
(more)
over 4 years ago
Edit Post #277306 Initial revision over 4 years ago
Answer A: How should we share some content between two otherwise-independent git repositories?
Generally speaking, if two groups of people collaborate on the same software, I'd recommend they put everything in a shared git repository: Documentation is intimately tied to the version of the software it describes. Looking at code examples in version X while writing docs for version Y is gener...
(more)
over 4 years ago