Search type Search syntax
Tags [tag]
Exact "words here"
Author user:1234
user:me (yours)
Score score:3 (3+)
score:0 (none)
Answers answers:3 (3+)
answers:0 (none)
isaccepted:yes
hasaccepted:no
inquestion:1234
Views views:250
Sections title:apples
body:"apples oranges"
URL url:"*.example.com"
Favorites infavorites:mine
infavorites:1234
Status closed:yes
duplicate:no
migrated:no
wiki:no
Types is:question
is:answer
Exclude -[tag]
-apples
For more details on advanced search visit our help page
Results tagged with Search options user 64132

For questions relating to the process of developing software.

5
votes
You're trying to use a bulldozer to hoe a garden. Stop it. The client & your management are happy with the current (primitive, simple, dangerous) process. This process works for a small app with a …
answered Apr 11 '14 by Dan Pichelman
4
votes
In a perfect world, your code wouldn't know if it's in test or production. In that same perfect world, your colleagues would know better than to use a service for production before it is ready. Sinc …
answered Jan 13 '17 by Dan Pichelman
20
votes
The shop has a disease called Not Invented Here. It is a good reason to terminate the interview on the spot and leave immediately. This can only be cured by a top-down house cleaning that is very un …
answered Apr 20 '13 by Dan Pichelman
1
vote
Recognizing that there's a better way than trial & error is the first step. I usually start with paper & pencil. I get a rough sense of what the client's asking for and sketch out the User Experie …
answered Sep 9 '13 by Dan Pichelman
7
votes
You only get one chance to make a first impression. If you release an obviously unfinished buggy app, the first people to look at it will drown you in negative reviews. Once you have a lot of nega …
answered Oct 3 '16 by Dan Pichelman
3
votes
I like Ike's answer to your original question. In short, you tackle the problem much like a mouse eating an elephant - you take one bite at a time, and accept it's going to be a very long process. F …
answered Nov 29 '17 by Dan Pichelman
21
votes
As noted in the comments, size of the binary could be very important for some embedded systems - especially old ones. However, as you've noted in the update to the question There is no customer o …
answered Nov 17 '15 by Dan Pichelman
6
votes
Short answer: No. Longer answer: If your refactorings are truly improvements, then you're engaging in Codependent behaviour - you're supporting your collaborator's bad habits & not giving him/her th …
answered Feb 11 '15 by Dan Pichelman
2
votes
Beta releases are by definition "works in progress". Until the vendor (Apple in this case) formally releases the software, there are no guarantees as to what will be in the final release (a feature m …
answered Mar 27 '18 by Dan Pichelman
7
votes
I document their activities, give them multiple written warnings, work with HR to create and implement an improvement plan, then I fire them. edit Since you're not the manager, the best you can do i …
answered Sep 5 '13 by Dan Pichelman