|
geeves posted:I can't bring myself to do this at the office. Usually when I'm at the point that I need to do this, I just message someone and ask to bounce ideas off of them. They know me well enough it will take about 5 seconds before I talk myself into the answer. It's usually just the process of organizing my thought train for someone else and stepping away from my desk that reveals the answer. Force yourself to have a conversation with an object, or if you can't do that, write something to yourself, or even just go somewhere and pretend to have a conversation on the phone. Messaging someone else, even if you figure it out in 5 seconds or just by walking away, still disrupts the flow of other people unnecessarily, which is why rubber duck debugging is so great.
|
#
?
Jul 27, 2017 11:23
|
|
|
|
| # ? May 10, 2024 10:27 |
|
|
Pollyanna posted:"So why did the design team not think through the inconsistencies of this front-end design?" Do you work for the same company I work for?  Except for CEO instead of CTO.
|
|
#
?
Jul 27, 2017 11:29
|
|
|
metztli posted:Force yourself to have a conversation with an object, or if you can't do that, write something to yourself, or even just go somewhere and pretend to have a conversation on the phone. I write detailed emails to one colleague whose opinion I respect and end up only sending < 20% of them because just writing it all out often lets me see the issue. And I feel like an email is easier for him to ignore until he's ready than IM or whatever, also I can search it later if it actually turns out to be something complex and ongoing.
|
|
#
?
Jul 27, 2017 11:54
|
|
|
Carbon dioxide posted:I have a coworker who explains the more complex frameworks we use to her three year old kid at home. "Uh, I tink yu neeEEEeeeEEEeeeed anudder abtractshun layah!"
|
|
#
?
Jul 27, 2017 14:00
|
|
|
Maluco Marinero posted:I can only hope you're not doing much front end development, for the kid's sake. The kid will demand to change schools when he hears that another school's cafeteria is offering a slight variation of his current school's pizza and that everyone can't shutup about it.
|
|
#
?
Jul 27, 2017 15:45
|
|
|
Carbon dioxide posted:I have a coworker who explains the more complex frameworks we use to her three year old kid at home. https://www.youtube.com/watch?v=RnqAXuLZlaE
|
|
#
?
Jul 27, 2017 16:22
|
|
|
Dirty Frank posted:I write detailed emails to one colleague whose opinion I respect and end up only sending < 20% of them because just writing it all out often lets me see the issue. And I feel like an email is easier for him to ignore until he's ready than IM or whatever, also I can search it later if it actually turns out to be something complex and ongoing. Not a bad idea - that way you still have it written out if you need it. Does anyone else find that actually verbalizing helps you differently than writing? I find verbalizing works best for me and writing it out is less successful at triggering the aha moment. Conversely, having to write out something that I already understand and need to explain to someone else is vastly easier for me than verbalizing it.
|
|
#
?
Jul 27, 2017 22:58
|
|
|
Volguus posted:Personally I believe that pair programming is great for mentoring (regardless who is actually writing the code) and is great for those times when "I have this really tough problem, let's solve it together on the computer instead of the whiteboard". Other than that, is a bit of a waste of time in my opinion. Yes, those are the two great reasons to pair program. But they can be applied to almost all your tasks (which isn't to say you should pair program on every task). If both people find a task hard, immediate feedback makes the cost of changes much lower than at the code review stage, which ultimately expedites the time it takes to build and launch. If one person finds a task hard, it's a good opportunity to transfer knowledge. Ever been in a scenario where one dev knows everything about how production works, and then they leave the company? Transferring knowledge introduces redundancy in your team, and expedites the time it would take to complete a similar task in the future. If both people find the task easy, you'd ideally find a person that doesn't. If everyone on your team finds most of the team's assigned tasks easy, it's a good idea to review your team structure. Clustering all your senior devs on one team means you miss out on opportunities to mentor junior devs. The mistake people make in assessing the usefulness of pair programming is assuming the direct outcome will be 2 "work units" (story points, whatever). Many of the actual benefits are indirect and may take some time to realize. (Another more minor benefit comes from seeing how other programmers -- of any level -- work. It's helpful to see the wide world of tools, tricks, and hacks programmers employ in the day-to-day work you might not even think about. And this sometimes even allows a junior dev to teach a senior dev something cool.)
|
|
#
?
Jul 28, 2017 00:14
|
|
|
Pie Colony posted:(Another more minor benefit comes from seeing how other programmers -- of any level -- work. It's helpful to see the wide world of tools, tricks, and hacks programmers employ in the day-to-day work you might not even think about. And this sometimes even allows a junior dev to teach a senior dev something cool.) this is the reason I know any of the keyboard shortcuts I know in my editor You enumerated all the reasons why I find it so valuable very well - but I also find that it becomes a speed multiplier simply because people aren't willing to make others sit through the kind of long deliberation they would be fine with on their own. A coworker of mine is a very talented dev, but tends to waffle on implementation details, because he tries to think through every possible use his code would have. When pairing, he'll quickly make decisions because of the pressure of someone watching him code. I used to work at a place where there was enforced pairing and I wish there were more places like that. Otherwise, the people who enjoy pairing self-select and the people who could benefit the most don't. Or people others could benefit from the most (thinking of the lead dev who has the entire codebase in his head).
|
|
#
?
Jul 28, 2017 00:59
|
|
|
metztli posted:Not a bad idea - that way you still have it written out if you need it. Yep. That's why I tell people to actually *talk* to the duck. My understanding is that talking aloud has you using different pathways in the brain, which will help you make new connections with the problem.
|
|
#
?
Jul 28, 2017 00:59
|
|
|
The Cavern of COBOL > Working in Development: That's why I tell people to actually *talk* to the duck.
|
|
#
?
Jul 28, 2017 07:17
|
|
|
geeves posted:The kid will demand to change schools when he hears that another school's cafeteria is offering a slight variation of his current school's pizza and that everyone can't shutup about it. They'll redo the term 4 times to keep up with the latest educational trends, ending the year with only one completed term worth of work. Edit: then they'll decide with their wealth of experience in that term that they should write a curriculum, and make a nice website for it.
|
|
#
?
Jul 28, 2017 09:59
|
|
|
Anyone else bored at work? There's not enough work for me to do, so quite a bit of time browsing the internet. Starting to feel guilty.
|
|
#
?
Jul 28, 2017 23:16
|
|
|
Ither posted:Anyone else bored at work? That usually means either the project or the company is poorly managed enough for the place to start falling apart. Get your resume up to date. Sorry bud.
|
|
#
?
Jul 28, 2017 23:31
|
|
|
This time of year is very slow for some industries. Lots of executives take vacations in August.
|
|
#
?
Jul 28, 2017 23:42
|
|
|
I have nothing to do but that's because we are in regression and UAT testing and me and my team did an actual good job. Other teams are flooded with defects and I just laugh and submitted my 2 weeks.
|
|
#
?
Jul 28, 2017 23:47
|
|
|
Where are you headed?
|
|
#
?
Jul 28, 2017 23:56
|
|
|
Ither posted:Where are you headed? To a much smaller company where I will be taking over much more responsibilities. Which is a great opportunity to improve my skills.
|
|
#
?
Jul 28, 2017 23:59
|
|
|
lifg posted:This time of year is very slow for some industries. Lots of executives take vacations in August. Yeah, seriously. We do a lot of business with European ISPs, and everything just shuts down for the whole month of August. From an American standpoint, it seems insane. Wish I could take the month off too, though.
|
|
#
?
Jul 29, 2017 04:06
|
|
|
a foolish pianist posted:Yeah, seriously. We do a lot of business with European ISPs, and everything just shuts down for the whole month of August. From an American standpoint, it seems insane. To be honest, when I arrived in Canada and heard that the minimum required vacation days per year was 10 (while most employers were offering 15) I thought that was loving insane. How can anyone live with less than 25 working days per year of vacation, like normal people get? Then I heard about US. After 10 years and I still can't comprehend it. It is, as far as I can tell, an impenetrable mystery on why people put up with this. But yeah, August is dead. So is December.
|
|
#
?
Jul 29, 2017 05:38
|
|
|
Volguus posted:To be honest, when I arrived in Canada and heard that the minimum required vacation days per year was 10 (while most employers were offering 15) I thought that was loving insane. How can anyone live with less than 25 working days per year of vacation, like normal people get? Then I heard about US. In software at least you get decent pay.
|
|
#
?
Jul 29, 2017 13:41
|
|
|
Volguus posted:To be honest, when I arrived in Canada and heard that the minimum required vacation days per year was 10 (while most employers were offering 15) I thought that was loving insane. How can anyone live with less than 25 working days per year of vacation, like normal people get? Then I heard about US. I get 5 weeks paid vacation, but I suspect that's because Nokia, which just bought us, is a Finnish company. Prior to that, we were on the typical startup unlimited vacation plan where you actually are working on things and need to finish them and so don't take very much time off. We don't just all leave at the same time, though.
|
|
#
?
Jul 29, 2017 14:59
|
|
|
Yeah, I've gotten the "this time of year is very slow" spiel too. Especially for hiring purposes, since execs are all out and nobody wants to try and hire someone while they're on vacation. Which is fine, but JFC I want a new job already.
|
|
#
?
Jul 29, 2017 15:23
|
|
|
a foolish pianist posted:I get 5 weeks paid vacation, but I suspect that's because Nokia, which just bought us, is a Finnish company. Nokia must have given you a sweat-heart deal in you're in the US. They did start people with a decent 3 weeks, going up to 5 weeks over like a decade. I currently work for an unlimited company. Got approved for 2 1/2 weeks off around my 6 month mark for employment, plan on asking for another 2 weeks another 6 months after that and see how it goes.
|
|
#
?
Jul 29, 2017 21:27
|
|
|
July is crunch time on a massive project for my company, with all deliverables to be completed by the end of the month (else huge financial penalties apply). I have no idea how it's going, since I managed to book a lengthy holiday for this month . Haven't even checked my emails once. It's so loving great.
|
|
#
?
Jul 30, 2017 22:45
|
|
|
I'm gonna go ahead and guess that if nobody but your team leader can be trusted to approve a PR (thereby ensuring that it's in an acceptable state), then that team leader has done a poor job of disseminating knowledge and regulations of the code/system. If I have to get the team leader to go through every PR since only he knows what might break further down the line, then he hasn't shared enough knowledge with us and is siloed the gently caress off. What a pain.
|
|
#
?
Jul 31, 2017 15:30
|
|
|
Pollyanna posted:That usually means either the project or the company is poorly managed enough for the place to start falling apart. Get your resume up to date. Sorry bud. That said the company's still doing really well, we had our own offices in a really neat converted house overlooking the sea, and the work was really interesting...if it wasn't for the fact they paid peanuts (£18k/year in 2005) I don't think I'd ever have left. Where I am now it's crunch time pretty much all year round, but at just the right level where the work day flies by but you never feel like things are totally out of control. I'm much happier here, being busy.
|
|
#
?
Jul 31, 2017 16:02
|
|
|
Inheritance is a siren whose rocks I intend to stop crashing on.
|
|
#
?
Jul 31, 2017 18:24
|
|
|
I'm not smart enough to figure out how to handle time/dates and handle all the conversions from/to UTC/DateTimeOffset from the browser to moment to knockout to newtonsoft json to webapi to dapper to sql and back. Whoever invented time is an rear end in a top hat 
|
|
#
?
Jul 31, 2017 19:24
|
|
|
MisterZimbu posted:I'm not smart enough to figure out how to handle time/dates and handle all the conversions from/to UTC/DateTimeOffset from the browser to moment to knockout to newtonsoft json to webapi to dapper to sql and back. It's not you, all the tooling is bullshit. None of the layers make it easy to just do the right thing.
|
|
#
?
Jul 31, 2017 19:37
|
|
|
MisterZimbu posted:I'm not smart enough to figure out how to handle time/dates and handle all the conversions from/to UTC/DateTimeOffset from the browser to moment to knockout to newtonsoft json to webapi to dapper to sql and back. Timezones are subjective and require a perspective/context. Meaning, you always have to pass around the timezone you want to render the datetime relative to. Save with timezone, render with timezone, transpose if needed
|
|
#
?
Jul 31, 2017 19:55
|
|
|
MisterZimbu posted:I'm not smart enough to figure out how to handle time/dates and handle all the conversions from/to UTC/DateTimeOffset from the browser to moment to knockout to newtonsoft json to webapi to dapper to sql and back. The easiest thing to do is to not handle anything. Everything is UTC, until the moment of display. When sending it back, convert to UTC in the client. Then simply not worry about it. Otherwise you'll go insane.
|
|
#
?
Aug 1, 2017 00:21
|
|
|
Volguus posted:The easiest thing to do is to not handle anything. Everything is UTC, until the moment of display. When sending it back, convert to UTC in the client. Then simply not worry about it. Otherwise you'll go insane. I'm thinking of doing a talk on this, cause yeah ideally this is the ideal, but it depends on context. If you're entering opening times for a business, the user would expect the Timezone they're using to correspond to the one the business is in. Then there's client time reckoning vs server time reckoning, and how you sometimes need to use naive datetimes of communicating across document like formats such as spreadsheets, where the user would expect to see the exact same datetime no matter what the Timezone their client JavaScript is running in. It all depends on context as said, and boiling it down to the simplest possible case for the user, which is usually either wysiwyg naive datetimes, or utc datetimes where the client converts to local at the last moment. I think either way though, transport of datetimes should avoid anything clever. Keep them as simple ISO time strings as long as humanly possible, almost right up to the point of render, to keep as much context as possible for what you're rendering til the point of render.
|
|
#
?
Aug 1, 2017 01:07
|
|
|
Since our application didn't care about hour of the day, we did it so that if you picked Jan 15 12:00 AM Local Time, we would transpose that to Jan 15 12:00 AM UTC on the way to the server, and anything coming back would have to be transposed to Jan 15 12:00 AM Local. I really hated it. It created some weird situations for our client-side validation when dates were set in the future.
|
|
#
?
Aug 1, 2017 01:16
|
|
|
Funny thing is even well funded startups or enterprises still sometimes show me something I've uploaded/done as 10 hours in the future (I'm UTC+10), shits hard and no one is immune to tz inconsistency it seems.
|
|
#
?
Aug 1, 2017 01:28
|
|
|
Screw it, TAI everywhere. https://en.wikipedia.org/wiki/International_Atomic_Time
|
|
#
?
Aug 1, 2017 01:55
|
|
|
Swatch Time everywhere! https://en.wikipedia.org/wiki/Swatch_Internet_Time
|
|
#
?
Aug 1, 2017 01:56
|
|
|
Rubellavator posted:Since our application didn't care about hour of the day, we did it so that if you picked Jan 15 12:00 AM Local Time, we would transpose that to Jan 15 12:00 AM UTC on the way to the server, and anything coming back would have to be transposed to Jan 15 12:00 AM Local. I was this close to adding support for a date-only data type to the code and database at Experts Exchange before I looked at the potential uses the code would have and found all of them in the spaghetti that was the billing system.
|
|
#
?
Aug 1, 2017 01:57
|
|
|
My colleague and I were discussing the testing server the company gave us and how well it performs. I believe it must be running on an old shoebox. He disagrees, and thinks it's running on a potato. What do you goons think?
|
|
#
?
Aug 1, 2017 06:51
|
|
|
|
| # ? May 10, 2024 10:27 |
|
|
Carbon dioxide posted:My colleague and I were discussing the testing server the company gave us and how well it performs.
|
|
#
?
Aug 1, 2017 07:37
|
|
