201–210 of 213 posts
Earlier quoted context omitted.
put it in a stack then take it back out, first in last out.
Follow up is usually: now do that with O(1) memory.
Earlier quoted context omitted.
That article is here: http://www.onebigfluke.com/2016/04/whats-awful-building-soft... Referenced from this article.
Thanks for the link. A lot of the software engineer points in that article seem to be focused at the level of writing and maintaining code, but zooming out gives you the chance to look at the nature of a software development job.
Earlier quoted context omitted.
"on time" is a relative term. Assuming you show up, work your time, make your meetings and commitments and be a reasonably accountable person - no one will care what time you start the day whether it is 5am or 10am.
This is just not true. There are offices that have legitimate reasons for requiring employees to be there at certain times. I've worked in secured locations that were all but inaccessible at 6:01 pm and you needed a good reason to be there after 5. In an environment like that, you can't stroll in at 10:30 because you prefer to sleep in. A lot of folks on HN seem to have this idea that as long as you show up it should…
For me, it's a necessity. I have fairly severe circadian rhythm problems and getting to work earlier is asking me to be unproductive, depressed and tired.
Earlier quoted context omitted.
At some companies, you're right... I am seeing some stuff right now that blows my mind, complete incompetence getting promoted to executive levels. Unbelievable.
http://www.ribbonfarm.com/2009/10/07/the-gervais-principle-o...
Earlier quoted context omitted.
> .. until you started using it! I've been building stuff using GWT for the past 5 years, so I'm either doing it wrong or I'm completely missing something. So, what's wrong with GWT?
We have a large GWT code base, although others here work on it more than I do. Problems that seem to get mentioned a lot: 1. Difficult to develop or debug without custom IDE plug ins. With Google cutting back on their investment, not clear how well those plug ins will be maintained in the future. 2. Awkward to work with Javascript libraries, at least compared to all Javascript development. 3. Sometimes hard to predic…
Interesting, I'm just using IntelliJ IDEA and their GWT plugin.
What are they using?
> 2. Awkward to work with Javascript libraries, at least compared to all Javascript development.
Fair enough, it does take some getting used to it.
> 3. Sometimes hard to predict exactly what Javascript will be emitted for specific Java code.
I'm not sure why this matters?
I thought that's the idea when you add another abstraction layer.
> 4. Remembering the rules for what Java code can or cannot be compiled by the GWT compiler.
Oh I think I get it now, they haven't migrated to Super Dev Mode yet.
That way it no longer requires a browser plugin (the old devmode), and the code is just JS + sourcemaps.
And if you use code that can't be compiled, you know straight away, not just when doing a production compile.
> 5. A lot of indirection. The event model has definite benefits, but it also seems to make it very hard to figure out what the program will do by just navigating the code.
I don't agree with this, but I'm probably biased as a Java guy.
> 6. Difficult to find developers willing and able to work on a GWT code base.
I'm available :-P
But being serious, thank you for the write-up, you do have some good points.
Earlier quoted context omitted.
"on time" is a relative term. Assuming you show up, work your time, make your meetings and commitments and be a reasonably accountable person - no one will care what time you start the day whether it is 5am or 10am.
This is just not true. There are offices that have legitimate reasons for requiring employees to be there at certain times. I've worked in secured locations that were all but inaccessible at 6:01 pm and you needed a good reason to be there after 5. In an environment like that, you can't stroll in at 10:30 because you prefer to sleep in. A lot of folks on HN seem to have this idea that as long as you show up it should…
Earlier quoted context omitted.
Follow up is usually: now do that with O(1) memory.
This doesn't seem like a very valuable interview question anymore because it's well known and you can probably google the simple answer, but if not this is the basic idea (walk the list once pointing each next at the previous node and return the new head when you reach the end): List *Reverse( List *pList ) { List *pPrevious = nullptr; List *pCurrent = pList; while ( pCurrent ) { List *pNext = pCurrent->GetNext(); pC…
We ask these questions for a few reasons. You hope that the candidate hasn't seen it before, because you want to see their problem-solving process. You also want to see which questions they ask, which assumptions they make, etc. How well do they explain their thought process? Do they understand the algorithm, or did they rote-learn it?
Will they need to jump through algorithmic hoops writing a CRUD app? Probably not...but they'll need to solve problems creatively. It might be better to walk through an actual investigation+bugfix in a piece of software, but that takes more time to do (interviewer+candidate) and more effort (interviewer) to set up, so it's not surprising that most interviewers would take the easier way out.
Earlier quoted context omitted.
And there isn't one that I'd want.
What about being hired at CTO and tasked to improve the tech experience for all their stores? From connected services and employee efficiency due to better tech for making some of the meals, etc.
Earlier quoted context omitted.
I've never been a coal miner, but there is some sort of satisfaction in working with your hands that you don't quite get being a corporate coder.
There's also the black lung that you don't quite get being a corporate coder. I think it's very easy for people who aren't working with their hands every day to sit back and talk about the 'satisfaction' you get. You may get that if you go and do it for a day. When you're doing it every day you're destroying your back, knees, your hands end up cut and calloused, and you're exhausted. And the 'satisfaction' probably d…