|
anatoliy pltkrvkay posted:life is suffering and we are all trapped in samsara. if life is suffering and reality is cyclical why not break the cycle and reduce it all to nothing #YawningAbyss2020 Notorious b.s.d. posted:comfortable is a lot more achievable than happy i have learned this ![]() i miss my friends. i want more cats. and a gf that is not dead which can eternal lie, and with strange aeons even death may die
|
![]() |
|
![]()
|
# ? Feb 8, 2025 04:42 |
|
palate cleanser https://twitter.com/Shpigford/status/994583740943929346 https://twitter.com/duretti/status/995070687516680192 https://twitter.com/alicegoldfuss/status/994971564868190209 https://twitter.com/fembotswana/status/995246312491597825 never trust the boss man
|
![]() |
|
Progressive JPEG posted:those engineers should've lost their stamps for this!
|
![]() |
|
Pollyanna posted:never trust the boss man "Serial Founders" are just the worst in my experience. The early years of a company are basically fake it to you make it: lie, embellish, whatever you gotta do to convince the world that you and your two friends really are the market leader in dog boner analytics or whatever your business is. Then once you sucker some early customers or VC money you could (in theory) develop a real product. Serial founders are either bad at this, or enjoy the process of lying so much they make it a full time job. Neither one is good.
|
![]() |
|
Pollyanna posted:palate cleanser Both of these things are simultaneously true. Except for the conspiracy part. Overt conspiring with competitors to keep pay low is mostly limited to big name incidents like the Apple / Google scandal. In general, it's more like an incidental game of prisoners dilemma than secret midnight agreements.
|
![]() |
|
ADINSX posted:"Serial Founders" are just the worst in my experience. The early years of a company are basically fake it to you make it: lie, embellish, whatever you gotta do to convince the world that you and your two friends really are the market leader in dog boner analytics or whatever your business is. Then once you sucker some early customers or VC money you could (in theory) develop a real product. Extremely true
|
![]() |
|
TimWinter posted:Except for the conspiracy part. Overt conspiring with competitors to keep pay low is mostly limited to big name incidents like the Apple / Google scandal. In general, it's more like an incidental game of prisoners dilemma than secret midnight agreements. it's just a normal business practice to pay women less changing jobs more often means more raises, at the expense of a checkered resume and less impressive projects
|
![]() |
|
Notorious b.s.d. posted:it's just a normal business practice to pay women less you can't eat and live in impressive resumes tho
|
![]() |
|
Boiled Water posted:you can't eat and live in impressive resumes tho no it's a damned if you do, damned if you don't situation switching jobs frequently more closely aligns your pay with the market, but it can damage your career development. if you have no chance of getting a fair shake on raises then you are pretty well screwed either way
|
![]() |
|
TimWinter posted:Except for the conspiracy part. the conspiracy is patriarchy
|
![]() |
|
Pollyanna posted:if life is suffering and reality is cyclical why not break the cycle and reduce it all to nothing Creations are numberless, I vow to free them. Delusions are inexhaustible, I vow to transform them. Reality is boundless, I vow to perceive it. The awakened way is unsurpassable, I vow to embody it.
|
![]() |
|
Notorious b.s.d. posted:no it's a damned if you do, damned if you don't situation ![]()
|
![]() |
|
Tbh though if you've really got the plot, the new employer will catch on soon enough. The opposite side of the bed is an employer views you as too dogmatised to a company you spent say ten years with. I don't think switching companies is a big deal as long as it's not every couple of years and you stay focused on what you're good at and don't try to do everything.
|
![]() |
|
Notorious b.s.d. posted:it's just a normal business practice to pay women less I can't tell if this is sarcasm but there's no need for it to be. In my (limited) experience women get significantly more bullied around on salary than men, without the need for a conspiracy behind it.
|
![]() |
|
Salary bullying is terrible but it seems to be a good way to know how a maybe employer will think of you. That said do employers ever not act like shitheads then want you to commit to them? Holy poo poo
|
![]() |
|
Space Whale posted:do employers ever not act like shitheads nope.
|
![]() |
|
So it's a matter of how they treat you once you negotiate? Meh
|
![]() |
|
ADINSX posted:"Serial Founders" are just the worst in my experience. The early years of a company are basically fake it to you make it: lie, embellish, whatever you gotta do to convince the world that you and your two friends really are the market leader in dog boner analytics or whatever your business is. i wondered what 'pugspot' might be
|
![]() |
|
TimWinter posted:I can't tell if this is sarcasm but there's no need for it to be. In my (limited) experience women get significantly more bullied around on salary than men, without the need for a conspiracy behind it. not even a hint of sarcasm
|
![]() |
|
TimWinter posted:I can't tell if this is sarcasm but there's no need for it to be. In my (limited) experience women get significantly more bullied around on salary than men, without the need for a conspiracy behind it. Your posting makes me like qhat more.
|
![]() |
|
help I'm getting an intern how do find the happy medium between micromanaging and explaining everything down to where the power button on the computer is vs leaving them to the wolves
|
![]() |
|
fritz posted:Creations are numberless, I vow to free them. Tao called Tao is not Tao. Names can name no lasting name. Nameless: the origin of heaven and earth. Naming: the mother of ten thousand things. Empty of desire, perceive mystery. Filled with desire, perceive manifestations. These have the same source, but different names. Call them both deep - deep and again deep: The gateway to all mystery.
|
![]() |
|
Background: I'm pretty young and the intern goes to the same school I went to so I have a pretty good idea of where they're at in the curriculum, even if it's probably changed a little by now. The team I'm on is working on a new product that's a globally-distributed platform built on top of microservices so I'm thinking that teaching the new intern about some of the architectural decisions we've made and why we made them is a good place to start. They probably don't know a lick of C# but they know Java so I'm not worried about them being unable to even start writing code. I could teach them about some C# features like Linq, or maybe details about the CLR and JIT.
|
![]() |
|
jit bull transpile posted:Your posting makes me like qhat more. Heh, in this particular instance I'm talking about how my wife was successfully promoted to a position to replace someone who was paid 50% more, and myself witnessing the subsequent year and a half of amazingly underhanded bullying and dodging of salary discussions. I haven't seen anything like this at my current workplace, but there aren't many women employees in any of the teams I've been in (a different problem that the company has been trying to address, albeit with mixed results).
|
![]() |
|
ThePeavstenator posted:help I'm getting an intern how do find the happy medium between micromanaging and explaining everything down to where the power button on the computer is vs leaving them to the wolves I've found that just planning for the latter is a good move.
|
![]() |
|
ThePeavstenator posted:help I'm getting an intern how do find the happy medium between micromanaging and explaining everything down to where the power button on the computer is vs leaving them to the wolves ![]()
|
![]() |
|
|
![]() |
|
ThePeavstenator posted:help I'm getting an intern how do find the happy medium between micromanaging and explaining everything down to where the power button on the computer is vs leaving them to the wolves congrats you get to learn how to be a manager without having any real complications of you failing at being a manager because hey they're just an intern
|
![]() |
|
ThePeavstenator posted:help I'm getting an intern how do find the happy medium between micromanaging and explaining everything down to where the power button on the computer is vs leaving them to the wolves 0. Have a chat with them to see where they're at, learn to know them a little bit, see what gaps there may be in their knowledge. 1. set expectations on the kind of work they'll be doing. High level objectives of what you'd consider them to be demonstrating good progress over time. Is it okay for them to ask questions, and if they do, will you think less of them as an intern (the answer should be no, especially not early on; as time goes you may expect them to be a bit more self-directed but it's okay to feel lost at first). When is it okay to ask questions and interrupt you? What kind of work they might be doing, and so on. 2. ask them whether they have expectations, what they'd like to learn or push into. It's possible you'll get a shy answer like "well I don't know" or they may be stumped because what you had in mind for them isn't what they thought they'd be doing. It's possibly a good point to get that clear with them, see if there's any common ground 3. tell them about the tools you usually use, any standards you may have in code or procedures, and give them a tour of the tools. If you have relevant docs, send them links, and make sure they'll have time to get through a bit of them. Present them to the team so they're not afraid to talk to other people either even if you're their main point of contact At any step, let them ask questions or discuss things. If you find out you all develop on platforms they're not familiar with, you'll have to adjust your expectations and provide a different amount of guidance. If there's areas where they don't necessarily know stuff, you can probably show them the basics and broad lines, and then give references to more advanced docs if they need it. Really, talk to them, keep objectives and expectations clear, and also make it explicit that you want to help them succeed. Let them get comfortable with that kind of relationship and it might become a lot simpler to answer their specific needs rather than trying to balance more abstract concepts like over- and under-managing or explaining.
|
![]() |
|
Welp just spent 3 hours on leetcode trying to come up with a good algorithm for validating a binary tree, managed it, then checked other people's solutions and realised I could've just done in order traversal and checked the current value against the previous. I guess I'll be putting off that Amazon assessment for another day.
|
![]() |
|
qhat posted:Welp just spent 3 hours on leetcode trying to come up with a good algorithm for validating a binary tree, managed it, then checked other people's solutions and realised I could've just done in order traversal and checked the current value against the previous. I guess I'll be putting off that Amazon assessment for another day. three hours does seem long my favorite way for validating a bst is you start at the root with a clopen range [-inf,inf), verify that the root is in the range, then split the range by the root for the left and right nodes respectively and recurse
|
![]() |
|
FamDav posted:three hours does seem long How often is remembering in-order traversal and validation truly useful. Or what you suggested useful? I've literally never done anything with trees directly, just used collections that used them to do things like make it easy to search or get highest/lowest from a set. Databases have Trees but I don't interface with them directly. ![]() As far as codefights type poo poo finding the kth lowest was fun/interesting but nothing I've ever really done. Hell the one time I was playing with resorting a sorted or mostly storted list vs using heaps it was faster to do it the former way in practice ![]()
|
![]() |
|
Not that I want to turn this into a freestyle shoelace-tying contest but https://ghostbin.com/paste/bdzdu am I missing something here? ![]() Though speaking of cycles poo poo you'll never ever have to deal with in practice, loving tortoise and hare is something that literally never gets used outside of programming interviews. You end up with a linked list that may or may not be circular and you break out the memory debugger son cuz you really hosed up somewhere.
|
![]() |
|
FamDav posted:three hours does seem long I literally never do this poo poo. And even when I do (only for interviews) I forget it in a few months because I never do it (on the job).
|
![]() |
|
Sapozhnik posted:Not that I want to turn this into a freestyle shoelace-tying contest but You are missing something btw. This is the naive solution which is also incorrect. The root node has to be sure that every single node on the right (for example) is greater than itself. Your algorithm will report true on a right subtree even if the minimum value for the subtree is less than the root node.
|
![]() |
|
i saw a twitter post a little while back about questions to ask at startups for people who have only worked at large companies. i'm talking to a company that's much smaller than anywhere that i've worked so far and was wondering if anyone had opinions on these questions or anything else they would make sure to ask. source below, but copied and pasted because twitter sucks for this kind of thing. https://mobile.twitter.com/jensenharris/status/988967889330819072 tl;dr version: quote:1) How much money does the company have in the bank? quote:
|
![]() |
|
Good enough to add to the OP. I've been trying to push my company in the direction of having better answers to "The Questions" that are already there- they're good guidelines for a healthy organization, and startups have a notable, additional set potential pitfalls.
|
![]() |
|
just don't work at startups unless you have no other choice the pay will be lower than corporate america, the benefits will be crappier, the options are a crapshoot at best, leadership is invariably troubled, and startup business cultures are often toxic startups are bad places to work edit: the only reason i would ever advise anyone to consider working at a startup is that they are trying to dip their toe in the field, and they're starting from behind. e.g. someone coming in from another industry, or a fresh grad who hosed up and didn't get any internships startups are less picky about hiring, and they'll take a chance on a marginal or even flat-out bad candidate Notorious b.s.d. fucked around with this message at 19:06 on May 14, 2018 |
![]() |
|
Notorious b.s.d. posted:startups are less picky about hiring, and they'll take a chance on a marginal or even flat-out bad candidate I'm currently working at a startup. This is probably why ![]()
|
![]() |
|
![]()
|
# ? Feb 8, 2025 04:42 |
|
Not forgetting that the SDLC at startups very often sucks rear end completely.
|
![]() |