|
big corporate culture isn't necessarily bad. my experience at a big company that talks about that poo poo is that as groan worthy as it can be at they end of the day you probably get treated better than at a small company. results vary tho. i'm worried about moving from a huge corp. to a small company right now.
|
#
?
Sep 14, 2015 22:00
|
|
|
|
| # ? May 24, 2024 22:13 |
|
|
i've found at small companies you get a lot of autonomy, because the team is usually too small to have more than one or two developers attached to any one project. you can also work directly with stakeholders because the corporate structure is so flat, which is good and bad (communication is way better, but instead of one boss you may have a dozen). ymmv, my sample size is like three companies. i'm glad i did it for a while because you can learn a whole lot real fast, but i'm definitely ready for something a bit more structured.
|
|
#
?
Sep 14, 2015 22:15
|
|
|
rrrrrrrrrrrt posted:big corporate culture isn't necessarily bad. my experience at a big company that talks about that poo poo is that as groan worthy as it can be at they end of the day you probably get treated better than at a small company. results vary tho. i'm worried about moving from a huge corp. to a small company right now. i work in a small team, relatively disconnected from the parent org, quite disconnected from the big mega co it isn't so much working in a big company or a small one, it's working in a loosely coupled system, which is a lot easier when you're small
|
|
#
?
Sep 15, 2015 03:06
|
|
|
whatever system we have is horrendously, offensively, ludicrously bad de rigeur is every single program is destined to fail, fail gloriously, everyone knows this, in some cases it will not come to fruition for multiple years, but it's fine i dislike my job.
|
|
#
?
Sep 15, 2015 03:09
|
|
|
focal ischemia posted:Lot's of jobs in Wellington and Auckland for intermediate and senior positions though. are they really hiring for intermediate and senior positions, or are they advertising for intermediate and senior positions and then saying "we can't find anyone with the qualifications we need, we have to import people from abroad"
|
|
#
?
Sep 15, 2015 03:33
|
|
|
our company has a ton of people but seem to be more like small teams of 5-10 people. We requested a VM and deployed our own postgres server on it just last week. it feels like my last job at a small company except getting paid more, a real 401k, and stocks with value instead of a founder's hopes and dreams
|
|
#
?
Sep 15, 2015 04:43
|
|
|
eschaton posted:are they really hiring for intermediate and senior positions, or are they advertising for intermediate and senior positions and then saying "we can't find anyone with the qualifications we need, we have to import people from abroad" More importantly, how can I be one of these imported people? I've had enough of Japan's poo poo.
|
|
#
?
Sep 15, 2015 06:45
|
|
|
it must be pretty easy since 80% of my coworkers are imported
|
|
#
?
Sep 15, 2015 06:52
|
|
|
Got an email today, here is the subject verbatim: $PROJECT_NAME - Build # $BUILD_NUMBER - $BUILD_STATUS!
|
|
#
?
Sep 15, 2015 13:43
|
|
|
gonadic io posted:Got an email today, here is the subject verbatim: lol
|
|
#
?
Sep 15, 2015 13:46
|
|
|
i have an interview tomorrow and man am i impostering hard this loving suuuuuucks
|
|
#
?
Sep 15, 2015 14:09
|
|
|
gonadic io posted:Got an email today, here is the subject verbatim: looks like someone overescaped their jenkins vars
|
|
#
?
Sep 15, 2015 15:19
|
|
|
MALE SHOEGAZE posted:looks like someone overescaped their jenkins vars i miss jenkins 
|
|
#
?
Sep 15, 2015 15:27
|
|
|
Man, I just don't *get* C++ or OOP. I'm not even sure which. There's nothing you can say to help me I've got a deadline in a few hours and I've been holding back everybody else. Feels lovely. Just wanted to E/N post, thanks guys.
|
|
#
?
Sep 15, 2015 16:25
|
|
|
meatpotato posted:Man, I just don't *get* C++ or OOP. I'm not even sure which. There's nothing you can say to help me if your classmates seem to find it easier, it's because they've done other, similar stuff previously, and they can transfer their experiences. meatpotato posted:I've got a deadline in a few hours and I've been holding back everybody else. Feels lovely. coffeetable fucked around with this message at 16:33 on Sep 15, 2015 |
|
#
?
Sep 15, 2015 16:31
|
|
|
(well unless your teammates are assholes, in which case they're getting their comeuppance by being held back)
|
|
#
?
Sep 15, 2015 16:32
|
|
|
coffeetable posted:classmates I'm employed  My teammates are nice and help as much as they can but we have a rushed schedule and I've been bothering them too much anyway. I usually do embedded stuff in C, but that's about it. Now I'm writing a bunch of classes for a network protocol in babby's first C++11 that are supposed to work on both embedded and real-computer systems. If anything it's been a real eye-opener 'cause I was starting to get comfortable with my C stuff.
|
|
#
?
Sep 15, 2015 16:43
|
|
|
meatpotato posted:Man, I just don't *get* C++ or OOP. I'm not even sure which. There's nothing you can say to help me dude it's probably the oop. i'm like babby's first hobby programmer so i'm sure it was easier for many but it took me several different books and hearing it outlined/explained several ways before i really started to "get" oop. it just seems like a difficult concept, especially if you already have experience in the procedural stuff even harder to do a new language and that at the same time i'd bet. don't be too hard on yourself!
|
|
#
?
Sep 15, 2015 16:52
|
|
|
meatpotato posted:Man, I just don't *get* C++ or OOP. I'm not even sure which. There's nothing you can say to help me oop isn't as complicated as it gets made out to be, but it can be a bit weird if you're not used to it. here's kind of how i think about it: - your language provides a set of generic tools (primitive types and standard library functions) - objects let you build your own tools that are specific to whatever problem you're trying to solve out of those generic tools (classes usually) - now you can write your application code using your objects instead of the language's generic tools, which makes the intent of your code clearer vs. working directly with the lower-level stuff there's obviously more to it than that, but thinking about it as just building a domain specific language vs. thinking about the implementation details might help.
|
|
#
?
Sep 15, 2015 16:59
|
|
|
I had a hard time trying to understand OOP, and when it finally clicked I kinda had the feel that I didn't like it that much... with that said, C++ is special in how every detail has the potential to be specially convoluted. you should've played with C# or Java before tackling C++ imo
|
|
#
?
Sep 15, 2015 17:47
|
|
|
oop takes your functions and structs and says "these should probably go together most of the time"
|
|
#
?
Sep 15, 2015 18:59
|
|
|
on the other hand, templates take your functions and your structs, throw them up in the air, and puke 500-line errors all over you because you forgot a comma
|
|
#
?
Sep 15, 2015 19:06
|
|
|
Bloody posted:oop takes your functions and structs and says "these should probably go together most of the time" Understood, I sometimes write C like that for device drivers and it can work well in my simple mind. I even know how a vtable works (yeah, I know that's not impressive) it's just understanding how to use things like inheritance to my advantage, not disadvantage in a design that are hard. I'm pissed off, I don't know poo poo about good OO architecture so here I am refucking the interfaces and relationships of these same objects for the Nth time in the last week because it "doesn't feel right" or because I didn't realize it needed to also do X and that screws everything up. Yes I have Meyers' and the GoF books. No, I don't have time to read AND understand enough in time without an adderall prescription. My co-workers are leaving me in the dust, even the new hire straight out of school (I've been here two years). Though I can poo poo on him because he doesn't bat an eye about committing code that causes dozens of compiler warnings (using int32_t as a pointer, wtf) or having a bunch of excessively-scoped (even global) variables all over his sources. Goddammit I just want to quit this tech bullshit, the IoT can go straight to hell for all I care. /rant Hunter2 Thompson fucked around with this message at 19:32 on Sep 15, 2015 |
|
#
?
Sep 15, 2015 19:27
|
|
|
meatpotato posted:Understood, I sometimes write C like that for device drivers and it can work well in my simple mind. I even know how a vtable works (yeah, I know that's not impressive) it's just understanding how to use things like inheritance to my advantage, not disadvantage in a design that are hard. It's OK to let code not feel right, often I find that a new use for an object or design decision doesn't quite fit, but that's OK. If your code models the problem domain perfectly and without rough edges you're either brilliant or your problem is of a very specific type. Even simple problems can be difficult to solve in a way that feels right, see FizzBuzz
|
|
#
?
Sep 15, 2015 20:01
|
|
|
meatpotato posted:Understood, I sometimes write C like that for device drivers and it can work well in my simple mind. I even know how a vtable works (yeah, I know that's not impressive) it's just understanding how to use things like inheritance to my advantage, not disadvantage in a design that are hard. Does your company do code reviews? Design reviews? I'm assuming not, which is unfortunate. Going through the process of saying what you actually want to do and having someone whose "done poo poo" look it over is immensely helpful. it also gives new hires (like you) a reference for how to plan big poo poo. code reviews are helpful for refining your day to day coding style, as well as providing extra eyes.
|
|
#
?
Sep 15, 2015 21:45
|
|
|
wish my "code" was "reviewed" if you know what I mean
|
|
#
?
Sep 15, 2015 21:58
|
|
|
wish your "posts" weren't "viewed"
|
|
#
?
Sep 15, 2015 23:05
|
|
|
groan
|
|
#
?
Sep 15, 2015 23:10
|
|
|
Soricidus posted:wish your "posts" weren't "viewed" gotta check the colour and consistency of your posts though, just in case!
|
|
#
?
Sep 15, 2015 23:14
|
|
|
meatpotato posted:I'm pissed off, I don't know poo poo about good OO architecture so here I am refucking the interfaces and relationships of these same objects for the Nth time in the last week because it "doesn't feel right" or because I didn't realize it needed to also do X and that screws everything up. the best book I've found for introducing OO was the first half of NeXT's "Object-Oriented Programming and the Objective-C Language" — the first half was all about OO and decomposition and stuff like that, was only a few dozen pages, and I saw it get a lot of people over the hump even without bothering with the Objective-C language parts the successor was split into two books, the first "Object-Oriented Programming with Objective-C" still doesn't have much Objective-C stuff in it and has generally preserved the good things about the original book. it'll be worth taking some time out for the 30-60 minutes needed to read the parts on OO concepts. also, the book was originally written mostly for people with some C/UNIX experience, which it sounds like you have, so there's still a lot of "this is kind of like ___ in C, but with ___ too." eschaton fucked around with this message at 23:29 on Sep 15, 2015 |
|
#
?
Sep 15, 2015 23:26
|
|
|
I mostly don't use inheritance because it is frequently the wrong tool
|
|
#
?
Sep 15, 2015 23:58
|
|
|
if you make two or three distinct things and realize a lot of your code looks the same now you might want to consider inheritance
|
|
#
?
Sep 15, 2015 23:59
|
|
|
"Rule of three" is a pretty good rule.
|
|
#
?
Sep 16, 2015 00:31
|
|
|
Bloody posted:I mostly don't use inheritance because it is frequently the wrong tool last Friday I wrote my first abstract class. it lasted around 25 minutes before i thought "wtf am I doing" and changed it to an interface and a couple of static methods
|
|
#
?
Sep 16, 2015 00:36
|
|
|
CPColin posted:"Rule of three" is a pretty good rule. I go by the "Rule of two" because two copies of the same code have been more than enough to gently caress me over in the past.
|
|
#
?
Sep 16, 2015 00:37
|
|
|
Bloody posted:I mostly don't use inheritance because it is frequently the wrong tool I use it a lot because I am a frequently-wrong tool
|
|
#
?
Sep 16, 2015 00:39
|
|
|
today, i extracted an interface from a class because i wanted to stub in a mostly-the-same-but-different-enough version of the class over it without getting rid of the original one. it leaves most of the methods undefined and i don't care worksformewontfix
|
|
#
?
Sep 16, 2015 00:56
|
|
|
Bloody posted:today, i extracted an interface from a class because i wanted to stub in a mostly-the-same-but-different-enough version of the class over it without getting rid of the original one. it leaves most of the methods undefined and i don't care worksformewontfix if your language has first-class functions, just pass that poo poo like it's a fat blunt and you're a good friend
|
|
#
?
Sep 16, 2015 01:03
|
|
|
eschaton posted:the best book I've found for introducing OO was the first half of NeXT's "Object-Oriented Programming and the Objective-C Language" — the first half was all about OO and decomposition and stuff like that, was only a few dozen pages, and I saw it get a lot of people over the hump even without bothering with the Objective-C language parts i remember when I first "got" OO and it was a real  moment.ue4 is nice for oo coz things are objects i lIKE IT
|
|
#
?
Sep 16, 2015 01:12
|
|
|
|
| # ? May 24, 2024 22:13 |
|
|
YOSPOS Terrible programmers are good friends  I printed out the Apple and NeXT manuals on my work's dime. I'm going to roll them into a huge spliff and smoke until I understand.
|
|
#
?
Sep 16, 2015 01:15
|
|