deeteecee

Yes, it does depend. My recommendation would still be to follow up with what I said and master the common ones used for basic conversation first. Then work on the rarer ones that pop up in the news or when you're renting apartments or whatever.

I'd stick to the common ones, you don't need to learn them all.

Your explanation was a bit unclear in the beginning but I think I got the point. From my perspective, you're describing two skilled coders (neither bad) but asking about the speed tradeoff, neither being bad.

I try to be that ideal programmer that switches between being both the fast or slow programmer and situationally adapts depending on the climate of the product and the company.

Who would I hire?

The ideal programmer if I can find it but otherwise, I'd just hire a mix of both.

Thoughts in my head:

* They should be aware from the onset that this requires investigation first of all. You would provide them with an update to see if you can actually timebox it midway into the process (be that the EOD or on another day)

* After having recognized that this problem was just a configuration issue, one should write down why that bug was so difficult to find and what is the work to be done to make that issue more visible?

* Speak to your personal manager and talk through the problem. Maybe they can share the insights with the management team.

Yeah, it's definitely not gonna be that explicit. There's a section under Cover called "Introduction to the Guide" that explains their objectives.

Anyways, this doc is gonna be useful for me because while I took computer science & engineering as a major in college, I never ended up taking a course that taught me how to holistically look at software engineering as a discipline and all the terms that come with it.

It doesn't look like you don't like working but similar to everybody, we have other things we would've loved to do that doesn't generate the income.

Anyways, I always thought big companies fit the bill for this even though I've only worked in startups myself. Actually, aren't sysadmin/IT roles also often great for near nothing? I'm also thinking about doing these jobs at places like schools/universities where expectations are low.

I don't see anything wrong with that but I do feel like you can still attain that same role but have it less overloaded. Maybe try a different company or share this with your boss?

I think I rarely read about people being burned out at Fortune 500 companies but saw your other comment that you aren't actually at one.

wanna just share the README and we can give some feedback?

i wouldn't care about it being boring but one thing I dislike about a lot of technical documents is I feel like there's always a simple way to translate it into simpler english.

Just don't attend them. Be honest and say you have work to do.

im still a young engineer but few thoughts:

* consider an alternative to confluence. that monster is unreadable especially if you have larger docs. also not enjoyable to edit and pretty much leaves all docs stale and unwanted.

* Do you have a proper README.md in every code base? That seems to be a pretty standard thing to do and as a developer, something I trust the most.

In my current team, I've had a tendency to proper document things because of our team's culture and way of doing things. It's just a shared mentality of doing things right.

same! im amazed it was still going and adding so many integrations.

It sounds like "talking to people" is the key point. How about just going out to social events and meeting people? There's also groups that focus on presentation skills as well if you wanted to improve on that aspect.

For me, as a software engineer, talking to people is actually a much needed skill. Part of that is because I work at a startup if that helps. Maybe you just need a work or culture shift but you can still do it with the same job.

I have my own personal document (any text editor would do) for notes attached to whatever I'm working on. What's on it depends on the task but usually, I write down all the things that need to get done and the status of where I'm at.

The notes I write aren't that specific to code though. Like, I'm not gonna write "I was looking at x file at code line y" but I'll write "Finishing serializer up" and any other notes that might help.

A pretty informative post. I like the mindset and towards the end, yup, the only big mistake that was made was not trying to switch to other teams at Stripe first. But certainly nothing wrong with switching jobs like that.

Live and learn.

I get what you're saying but in my view, it's more of a massive time sink. I think of it as having to spend many hours preparing for an exam. And I have to do this every time I switch jobs.

The algorithms and ideas do sort of stick to me somehow but I still have to repeat this silly exam prep over and over again. And it's sad because the truth is this part of the interview process has almost no relation to your actual job.

im pretty sure 99% of the time no one uses it that way lol.

I mean, i think you just need practice. i feel like you're thinking too literally about the basic process of programming and trying to apply it to sql.

Regarding table joins, this visual with venn diagrams on https://stackoverflow.com/questions/17946221/sql-join-and-di... usually helps me. But again, it's just practice. Try to think of real world cases and then creating relevant join statements for those.

That's a lot of points for an article that didn't say much. also, I question the author's experience of 10 years if he considered those hard questions to answer.

But point well taken, we want an easier and more usable tool. I definitely think the learning curve for beginners needs to be shaved off somehow.

it was never up for me :)

yep, im pretty sure they're just calling it 3D because of playing on a physical chess board but we can obviously play it in 2D. if i was creating the game, i would've done the same because of all those jokes about playing chess in multiple dimensions

i think it would be reasonable to just guide him to say "hey, you often just start off these online messages with 'hi.' can you just get to the point first?"

im in sf and we had a new contractor in india who wanted to ask about my PR comments and started with "hi." yeah...

I'm a bit confused by the article. It ended with a question about whether Brigade should keep that money but has only answered on the side of "Brigade is wrong. They should return the money back."

Is there a lot of work-related material surrounding you? I really just have my macbook and that's it. If that's not the issue, maybe just repeatedly remind yourself at a specific that time that work is over and to relax.

"We asked 950..." Okay I closed the article and left. I guess I'm surprised people keep saying they're surprised by the percentage and whatnot.

I feel like I'm reading my exact same thoughts from the past year. (Other than the "several hundred thousand a year." After talking to my manager, it sounds like metaphorically, I'm on poverty line in the software world)

Exercise helps me a lot, especially with our current situation. I don't see anything wrong with sharing it with your husband as long as you're rational about it.

Regarding work, do you still think about work when you go home? Are you able to drop those thoughts once you head home? I just write notes down first if I still have my thoughts in my head that I don't want to lose. More social interactions might help too but you'll likely have to be more proactive about it than other people to get it going.

that's good to hear. a bunch of smokers still smokin straight up in my face in sf

haha, curious what the actual context behind that statement is. one thing id ask them is does anyone on that team understand how that system works? also, what's the reason it was broken?

i drew one and it said "be more persuasive." i guess it wants more.

What made you drop out of the vocational school?