EPTThe Big Programming Thread - Page 499
| Forum Index > General Forum |
Thread Rules 1. This is not a "do my homework for me" thread. If you have specific questions, ask, but don't post an assignment or homework problem and expect an exact solution. 2. No recruiting for your cockamamie projects (you won't replace facebook with 3 dudes you found on the internet and $20) 3. If you can't articulate why a language is bad, don't start slinging shit about it. Just remember that nothing is worse than making CSS IE6 compatible. 4. Use [code] tags to format code blocks. | ||
|
Blisse
Canada3710 Posts
| ||
|
Encdalf
Germany66 Posts
On July 10 2014 15:26 Blisse wrote: Haha, I just learned if you have a mailto: link, if you populated the ?subject=&body= params, you can automatically prepopulate the email's subject and body when it is clicked and opened in the default mail client :d If you want you could specify a cc or bcc aswell, and enter the email in full spec with a display name. Something like... mailto:Mr.%20Foo%20%20Bar%3Cfoobar@example.org%3E?cc=foo.bar@example.org&subject=This%20is%20an%20email But it's rarely used.. | ||
|
Shield
Bulgaria4824 Posts
I think I'll just tell them that I've googled answers and that I probably don't want to work there. I don't think they could care about their graduate employees. Some of the questions were really stupid for a graduate though - CLR, Bitwise operators, how delegates are defined, etc. I doubt the first two are suitable for graduates. | ||
|
LaNague
Germany9118 Posts
Really basic questions are a very effective way to weed out applicants. | ||
|
aksfjh
United States4853 Posts
| ||
|
Blisse
Canada3710 Posts
| ||
|
urboss
Austria1223 Posts
| ||
|
Blisse
Canada3710 Posts
 I should really figure out how to use delegates. I'm also not sure what the "event" type is.. | ||
|
spinesheath
Germany8679 Posts
On July 11 2014 15:38 urboss wrote: I also just heard about these terms, you apparently only need them for Microsoft stuff. Certainly not. Events are used in a lot of languages, and some use them much more extensively (and probably better) than C#. A delegate is a typed method reference. No big deal here either. In the case of C#, you usually just use Action<T> and Func<T> to do your delegate stuff. | ||
|
Nesserev
Belgium2760 Posts
| ||
|
spinesheath
Germany8679 Posts
It's certainly not an ideal way, but apparently it's hard to come up with a better way for both sides, employer and applicant. Some thoughts on the topic: It's something that an applicant can kinda prepare for (good for his confidence in a stressful situation), and the employer can expect each good applicant to at least know what the questions are about. A specific applicant can shine by giving precise answers that show his clear understanding of the topic. If you pick hard questions, it becomes difficult to compare applicants. | ||
|
LaNague
Germany9118 Posts
Asking basic questions is a good way to see if someone studied to get trough tests or if he actually learned something. You dont need complex questions for that. This is of course assuming you ask them on the spot without them having preperation time or google | ||
|
Shield
Bulgaria4824 Posts
| ||
|
Cyx.
Canada806 Posts
On July 14 2014 03:15 darkness wrote: Speaking of Google, do you often look things up there when you're coding? What about at workplace, do you do it there too? All the time... is it possible to program without stackoverflow? | ||
|
Nesserev
Belgium2760 Posts
| ||
|
WoolySheep
Canada82 Posts
Anyone else experience this? | ||
|
8882
2735 Posts
On July 14 2014 03:56 Cyx. wrote: All the time... is it possible to program without stackoverflow? I think it is called: stackoverflow driven development  | ||
|
CatNzHat
United States1599 Posts
On July 14 2014 09:36 WoolySheep wrote: Just wondering if anyone else has experienced self-righteous, elitist coders at places they work? A lot of people I have worked with would always say "this code sucks", I should rewrite the whole thing", "The person who coded this was dumb", and it really ticks me off. Probably at the time of coding the idea was to do it a certain way but it has since changed. They tend to use fancy language and over-complicate issues in the attempt to sound smart. Anyone else experience this? A lot of code is shit, but unless it is going to positively impact the business to re-write it, then there's no reason to harp on it. That should be done during code review when the changes can actually be implemented. I lead a small team of engineers and act as the architect, and to help avoid these problems we always discuss and agree to implementation strategy beforehand, and if someone does something other than what we discussed it's written down somewhere for reference. If during implementation someone comes up with a better idea, they run it by me before continuing. In code review I basically look for two things: minimal changeset, and code clarity (how easy is it to tell what this code is doing without having to read every method being called). A lot of it comes down to naming things well and having consistent architecture. Having static code analysis to handle all the boring things like indentation, spaces after commas, .map vs .collect, etc... makes it much easier. Insulting the person who wrote the code is always a bad idea. Everyone writes shitty code, every time I go back and look at something I wrote a year ago, 6 months ago, last week, I always find things to harp on. That means I'm still learning. A lot of times the code doesn't need to be good, it just needs to get the job done. The code was written to solve a business problem, not for the sake of being a nice piece of code, and if the company wasn't making money at the time then there's very little reason to care about code quality. You don't even know if you'll need this functionality next week, why make it maintainable. | ||
|
artynko
Slovakia86 Posts
On July 14 2014 09:36 WoolySheep wrote: Just wondering if anyone else has experienced self-righteous, elitist coders at places they work? A lot of people I have worked with would always say "this code sucks", I should rewrite the whole thing", "The person who coded this was dumb", and it really ticks me off. Probably at the time of coding the idea was to do it a certain way but it has since changed. They tend to use fancy language and over-complicate issues in the attempt to sound smart. Anyone else experience this? Happens, all the time, and then when you check the commit history it was either the person complaining or you who did the stupid change. Everytime you have a look at a code that was written a year ago it will look like a retarded monkey wrote it. | ||
|
spinesheath
Germany8679 Posts
On July 14 2014 09:36 WoolySheep wrote: Just wondering if anyone else has experienced self-righteous, elitist coders at places they work? A lot of people I have worked with would always say "this code sucks", I should rewrite the whole thing", "The person who coded this was dumb", and it really ticks me off. Probably at the time of coding the idea was to do it a certain way but it has since changed. They tend to use fancy language and over-complicate issues in the attempt to sound smart. Anyone else experience this? I probably guilty of this, too. Though I never mean to insult anyone with it (and won't call anyone dumb or consider them to be dumb), it probably sounds like that to other people at times. When a piece of code is ridiculously tangled, or unintuitive information is implicitly duplicated across dlls, it makes my life hard and any change carries a huge risk to break existing functionality. Of course I have the urge to complain about that. Don't pass around instances of nice and informative classes as objects, don't return objects that could be strings or doubles or anything, don't cast around between enums, don't switch on types all over the place, and I'm a lot happier. It seems like most of my issues revolve around massive overuse of up- and downcasting... | ||
| ||
