EPTThe Big Programming Thread - Page 992
| 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. | ||
|
enigmaticcam
United States280 Posts
| ||
|
Silvanel
Poland4767 Posts
On January 25 2019 23:31 Acrofales wrote: Why don't you take a slice, figure out the query you want on the slice, and then once you got it mostly debugged, execute it on the full DB? There'll probably still be some bugs due to weird corner cases that weren't in your slice, but at least you won't have to wait 20-30 minutes *every* time you want to test a query. That is exactly same question i wanted to ask. I dont know anything about databases but this is generally a known problem (not only in computer science). If a data set is too large You slice it down and and analyse smaller chunks. Is there a good reason why You cant do that for databases? | ||
|
Manit0u
Poland17774 Posts
On January 26 2019 17:40 Silvanel wrote: That is exactly same question i wanted to ask. I dont know anything about databases but this is generally a known problem (not only in computer science). If a data set is too large You slice it down and and analyse smaller chunks. Is there a good reason why You cant do that for databases? We did use slices, but even those had billions of records in them since the problem at hand was so vague that we didn't really know what we were looking for and had to gradually narrow it down. In any case, it turned out that we most likely do not have data in the db that could solve the issue so we went back to the drawing board. This now means more reverse engineering for me since no one at the company really knows how the system is working (they fired all the people who created it 2 years ago) so I have to figure it out for them based on the code alone (stuff I'm dealing with now either has no documentation or docs are so outdated that are essentially worthless). | ||
|
spinesheath
Germany8679 Posts
| ||
|
Manit0u
Poland17774 Posts
On January 27 2019 17:24 spinesheath wrote: Did they also fire the person responsible for firing those devs without ensuring that their knowledge is not lost? Even from a pure business perspective, that sounds like a terrible decision. You don't have to tell me. They've fired 35 people, then discovered that they might still need developers so they hired me and one other guy in their place... | ||
|
Deleted User 3420
24492 Posts
| ||
|
enigmaticcam
United States280 Posts
On January 29 2019 02:23 travis wrote: Digging my schedule for this semester. Abstract algebra, elementary theory of computation(studying runtimes), cryptology, intro to deep learning These are all the classes I would love to take if I actually had time to go back to school. | ||
|
Deleted User 3420
24492 Posts
Basically, I have a class where all the assignments are in whatever language I want. So I want to learn something new. R or Go? | ||
|
Excludos
Norway8263 Posts
On January 30 2019 01:02 travis wrote: Does Go have a promising future? Which looks better on a resume for someone interested in ML, being fluent in python and Go, or being fluent in python and R? Basically, I have a class where all the assignments are in whatever language I want. So I want to learn something new. R or Go? For ML? R for sure. Together with Python those are the two most used languages within the field. | ||
|
Broetchenholer
Germany1962 Posts
"SELECT EXISTS(SELECT * FROM soldstock WHERE gameId = ? AND stockId = ?)" it returns 0 or 1 depending on the condition and the actual return value is something like "[RowDataPackage { "SELECT EXISTS(SELECT * FROM soldstock WHERE gameId = ? AND stockId = ?)":0}] I now convert this to JSON and then i could theoretically access it with result[0]['SELECT EXISTS(SELECT * FROM soldstock WHERE gameId = ? AND stockId = ?)']. Which is ridiculous. Is there an easier way for this? Can i name the result of my query in SQL? | ||
tofucake
Hyrule19224 Posts
| ||
|
Broetchenholer
Germany1962 Posts
 | ||
|
tofucake
Hyrule19224 Posts
| ||
|
Manit0u
Poland17774 Posts
Unrelated: Some good tips in there. | ||
|
Broetchenholer
Germany1962 Posts
| ||
|
Lmui
Canada6223 Posts
On January 30 2019 01:24 Broetchenholer wrote: hey guys, quick question concerning JSON objects from SQL. I have a SQL query that does not return a field value, it's an Exists query. Something like this: "SELECT EXISTS(SELECT * FROM soldstock WHERE gameId = ? AND stockId = ?)" it returns 0 or 1 depending on the condition and the actual return value is something like "[RowDataPackage { "SELECT EXISTS(SELECT * FROM soldstock WHERE gameId = ? AND stockId = ?)":0}] I now convert this to JSON and then i could theoretically access it with result[0]['SELECT EXISTS(SELECT * FROM soldstock WHERE gameId = ? AND stockId = ?)']. Which is ridiculous. Is there an easier way for this? Can i name the result of my query in SQL? Late to the party but agreed on aliases - https://www.w3schools.com/sql/sql_alias.asp You could also do SELECT <column> in the subquery instead of select *. The database should optimize it as you don't use the result of * but better to be explicit. I personally always delegate anything I can to the database. It's far more efficient at crunching data than your JS app since people smarter than you or me have done a lot of research into making it quick at getting data back. | ||
|
Manit0u
Poland17774 Posts
![[image loading]](https://i.imgur.com/wh6FtBr.jpg) Edit: In other news, one company posted some ridiculous demands by their programmers. They got the new guy a starter kit: MacBook Pro, iPhone Xs 256GB, magic mouse and keyboard. He was unhappy because they got it in silver instead of space gray so they had to send it back and order again... Bonus: https://vim-adventures.com/ | ||
|
Silvanel
Poland4767 Posts
| ||
|
Manit0u
Poland17774 Posts
On January 31 2019 23:38 Silvanel wrote: Since i am now running our teams testlab and one person just left our company i will be participating in a interviews for hiring new people. First time being on that side of interview i am already quite nervous! Tips? Just remember people on the other side will be more nervous than you most of the time. Try to ask broad, general questions rather than super specifics (unless required by the position). This should give you a general idea if a person is knowledgeable enough to perhaps find the correct solution on the web if they don't know out of hand. | ||
|
Lmui
Canada6223 Posts
On January 31 2019 23:59 Manit0u wrote: Just remember people on the other side will be more nervous than you most of the time. Try to ask broad, general questions rather than super specifics (unless required by the position). This should give you a general idea if a person is knowledgeable enough to perhaps find the correct solution on the web if they don't know out of hand. Entry level, I ask questions based on projects and try to assess their ability to learn. Probably 90% of new grads will be comfortable in one language, and have familiarity with one more. This means I just assess their existing technical ability, and then try and judge their ability/willingness to learn. I'm not senior enough to interview/assess people other than entry level. Agreed with Manit0u, try to ask questions around how they resolve problems. ex. When working on the project X you mentioned in the resume, what were the biggest challenges you came across and how did you resolve them. Could you tell me about a time where you didn't know how to perform a task, but learned something in order to do it? Describe. Depending on how they answer, you can dive deeper. It's always weird being an interviewer when you're new. Where I work, we try to have 3 people in the interview,1 manager, 2 technical interviewers and an optional 4th shadow. Anyone can shadow, whether junior, intern or senior engineer because it's useful to learn different interviewing styles and see what works for you. I shadowed something like 4 different people interviewing before I actually did my first one, and I found that super helpful in getting comfortable with it. Some people like very rigid structured interviews, and others prefer to start from one or two questions and expand out from there ad-hoc. | ||
| ||
