|
B-Nasty posted:The beauty of the VS extension I posted is that the HTTP requests are just simple text files (or multiple per file) that can be read by anyone and committed to VCS, etc. Postman makes this intentionally annoying to do to push users to storing their HTTP call config in the I've just started changing over to Spacemacs (vim habits die hard), and now I see there's a restclient equivalent for emacs (it might have even been first) and I'm probably gonna use this exclusively now instead of Postman for exploratory API work. It's kinda bewildering to look at the 'productizing' of a useful app to the point where they need 32+ people actively working on the thing. It's not enough to have a strong niche anymore, everyone's gotta own the space.
|
#
?
Jan 27, 2018 22:02
|
|
It's the classic case of a free, useful tool becoming productized and extended to the degree where it now misses the original point.
|
|
| # ? May 13, 2024 00:13 |
|
|
I use Postman at work and I've only just started using it and I don't know enough about HTTP to call it good or bad.
|
|
#
?
Jan 28, 2018 14:12
|
|
|
Ape Fist posted:I use Postman at work and I've only just started using it and I don't know enough about HTTP to call it good or bad. just use the vbcode pugin before you get used to postman
|
|
#
?
Jan 28, 2018 19:07
|
|
|
The underlying functionality is useful, it's just that it's become bloatware compared to what it was years ago.
|
|
#
?
Jan 28, 2018 23:21
|
|
|
I can imagine someone making an entire career out of continually implementing a basic functionality, making it popular, selling it off to a place that bloats the hell out of it, and then reimplementing it in a new application cause the old one got too big and lovely, rinse and repeat. A cycle of stupid.
|
|
#
?
Jan 29, 2018 01:39
|
|
|
Ape Fist posted:I don't use intellij so I'm not really qualified to tell you why you should. All I know is that the plugins are pretty fuckin' great and the soon-to-be released pair programming support is going to be huge. Live Pair Programming. This is the only reason I can think of to fathom switching from IntelliJ to VSCode. But I wouldn't full time. But if I had to program with someone remote, I'd switch over to VSCode for a while - and it's seriously not that bad from the 20 minutes I've spent using it. If / when Jetbrains makes live code sharing a feature I'll be very happy. However, I've also used Visual Studio and I absolutely hated it compared to IntelliJ.
|
|
#
?
Jan 29, 2018 02:21
|
|
|
geeves posted:Live Pair Programming. This is the only reason I can think of to fathom switching from IntelliJ to VSCode. But I wouldn't full time. But if I had to program with someone remote, I'd switch over to VSCode for a while - and it's seriously not that bad from the 20 minutes I've spent using it. If / when Jetbrains makes live code sharing a feature I'll be very happy. Heretic!  
|
|
#
?
Jan 29, 2018 05:43
|
|
|
Skandranon posted:Heretic! Well, when Jetbrains decides to listen to the proletariat and follow suit I won't have to worry about imperial distractions.
|
|
#
?
Jan 29, 2018 06:41
|
|
|
You could try writing an extension for it, but the extension docs kinda suck and I don't understand how anyone has ever succeeded at it
|
|
#
?
Jan 29, 2018 13:41
|
|
|
Pollyanna posted:I can imagine someone making an entire career out of continually implementing a basic functionality, making it popular, selling it off to a place that bloats the hell out of it, and then reimplementing it in a new application cause the old one got too big and lovely, rinse and repeat. A cycle of stupid. I know people that literally did this for 40 years and raked in tons of cash.
|
|
#
?
Jan 29, 2018 14:29
|
|
|
rt4 posted:You could try writing an extension for it, but the extension docs kinda suck and I don't understand how anyone has ever succeeded at it I had to debug an extension once and it wasn't too bad. For some reason I was just really really amused that the 'SDK' was you download the java source to the community edition of Intelli-J and run it in a debugger... That being Intelli-J itself.
|
|
#
?
Jan 29, 2018 14:35
|
|
|
I just discovered that Intellij has a REST client, but there's no convenient way to save and swap between requests like postman  (saving/loading from xml doesn't count)
|
|
#
?
Jan 29, 2018 14:41
|
|
|
VS Code and emacs both have good HTTP clients that can save and load files with request data if that's what you need
|
|
#
?
Jan 29, 2018 15:35
|
|
|
I kinda wish we had the enterprise Postman subscription because I work with semi-technical testing people and it'd be nice if they could just pull up the query I used and sub in whatever they needed in a pretty idiot-proof UI. Instead I have it generate cURL commands and paste them into the work item testing notes which ends up being a little error prone, especially if they have to edit JSON and keep everything escaped correctly
|
|
#
?
Jan 29, 2018 15:38
|
|
|
(a few weeks ago, during my first couple of days at my new job) Boss: "So why did you end up leaving your last job to come here?" Me: "They were really bad at giving me work to do. Every time I asked for a new task, they said they'd get back to me, but never did. My boss never fleshed out the few items we added to the backlog ourselves." (eleven days ago, before I left for vacation) Me: "It would really help me to capture all the ideas people have for new projects and upgrades to existing projects in a backlog, so I have less of a chance of running out of tasks." Boss: "Sounds good, I'll work on getting that together while you're out." (this morning) Me: *checks to see if my boss added anything to the backlog* 
|
|
#
?
Jan 29, 2018 17:44
|
|
|
What does "running out of tasks" look like for you? I had one job where I wasn't allowed to work on anything without authorization, and that was awful. Everywhere else, though, there's always things that can be done. Either devops work like getting the tests to run better or adding code coverage, or tech-debt work like some awful module that everyone's been meaning to fix up for years, or just asking everyone else "do you have anything I could help with?"
|
|
#
?
Jan 29, 2018 19:53
|
|
|
Mniot posted:What does "running out of tasks" look like for you? The only information I have is a vague list of projects and their relative priorities. I don't know what in the projects needs to be worked on. I'm also the only developer in the office, so there isn't anybody else to ask if they need anything. Fortunately, the stuff I was working on before I left appears to work fine, so I'm gonna deploy it today. Time to invent a deployment procedure (there isn't one written down, currently) and then stretch it to fill the rest of the morning! The guy I'm replacing has all kinds of things on his wishlist and I need him to write them down, too.
|
|
#
?
Jan 29, 2018 20:03
|
|
|
CPColin posted:I'm also the only developer in the office, so there isn't anybody else to ask if they need anything. Hahaha. Well if there's nothing that's bothering you and nobody has anything they want you to do, just find a couple open-source projects that you like and just work on them whenever.
|
|
#
?
Jan 29, 2018 20:17
|
|
|
An opportunity to improve the test coverage, perhaps?
|
|
#
?
Jan 29, 2018 20:19
|
|
|
CPColin posted:I'm also the only developer in the office, RUN AWAY! Seriously, you need other devs around you. Not even going to give you reasons as you know them already.
|
|
#
?
Jan 29, 2018 20:40
|
|
|
Or hire more devs because bouncing around jobs trying to find one that doesn't already suck is miserable. But what do I know.
|
|
#
?
Jan 29, 2018 20:41
|
|
|
Keetron posted:Seriously, you need other devs around you. Not even going to give you reasons as you know them already. Oh, I know. During the interview process, I mentioned feeling isolated as a big part of why I was leaving my previous job and made it clear that I was very apprehensive about being the only developer here. But it's a paycheck and the previous job wasn't going anywhere. It's another reason I want my boss to start putting together a long backlog, so it can stare everybody in the face and lead to us putting a team together.
|
|
#
?
Jan 29, 2018 20:51
|
|
|
CPColin posted:Oh, I know. During the interview process, I mentioned feeling isolated as a big part of why I was leaving my previous job and made it clear that I was very apprehensive about being the only developer here. But it's a paycheck and the previous job wasn't going anywhere. It's another reason I want my boss to start putting together a long backlog, so it can stare everybody in the face and lead to us putting a team together. Does you boss even know all the semantics and ritual that go into creating a backlog? Given you're the only developer at the place, you might be sounding like Charlie Brown's mom whenever you open your mouth about this stuff.
|
|
#
?
Jan 29, 2018 22:28
|
|
|
Rocko Bonaparte posted:Does you boss even know all the semantics and ritual that go into creating a backlog? Given you're the only developer at the place, you might be sounding like Charlie Brown's mom whenever you open your mouth about this stuff. That's possible. I've been showing her the GitHub project I made and describing how easy it is to add a "note" that's a short sentence describing something we want to do, including some examples I've added. I'm just now about to suggest that the outgoing developer add some stuff there, because he just sent an email with "I have a few small refinements in mind" in it.
|
|
#
?
Jan 29, 2018 23:08
|
|
|
CPColin posted:That's possible. I've been showing her the GitHub project I made and describing how easy it is to add a "note" that's a short sentence describing something we want to do, including some examples I've added. I'm just now about to suggest that the outgoing developer add some stuff there, because he just sent an email with "I have a few small refinements in mind" in it. Sounds like you don't have a PM, either. Unless you're planning to take that role for yourself, I think you may be getting ahead of yourself. With one developer and no engineering support, I would start by getting one or two high-level goals written down. Not something as engineering-focused as "more features in user profiles" but more like goals for the company. Then run yourself as an engineering department: come up with a couple engineering goals to support the company goal which you surface to your boss, and below that you can either run a whole scrum for yourself or just make it up day-to-day. When hiring, you'd get a handful of other engineers following you and then either look for a Product person or a manager to spend the kind of time it'd take to make a real backlog.
|
|
#
?
Jan 30, 2018 00:52
|
|
|
Mniot posted:With one developer and no engineering support, I would start by getting one or two high-level goals written down. Not something as engineering-focused as "more features in user profiles" but more like goals for the company. This is, more or less, what I'm trying to wring out of my boss and the outgoing guy right now. They keep mentioning how they want me to learn various systems and applications and I keep telling them I can't absorb and contextualize the information without knowing what I'm supposed to be doing with these things. There's a page on our internal wiki called "Colin's Training Topics and Priorities" that just lists the various systems again, without saying what sort of work needs to be done on any of them. I'm going to have to start getting more insistent with my requests for some sort of direction. And I'd be happy to put in some work as a PM, just to give me something to do!
|
|
#
?
Jan 30, 2018 01:12
|
|
|
CPColin posted:This is, more or less, what I'm trying to wring out of my boss and the outgoing guy right now. They keep mentioning how they want me to learn various systems and applications and I keep telling them I can't absorb and contextualize the information without knowing what I'm supposed to be doing with these things. Forgive me if this is obvious, but start documentation? Or find existing documentation, read through it, poke the system, and see where the documentation's outdated. Start putting up PRs for "Add setup to README"... "Update architecture doc"... or whatever. Or, check test coverage? Start figuring out what the testing situation is and filling in gaps, or reading through those.
|
|
#
?
Jan 30, 2018 02:13
|
|
|
So my first annual performance evaluation is coming up and I'm looking for a little insight. I work in the manufacturing industry where the base assumption when people are hired is that they plan to stick around for a long time. Obviously, being a SE I'm pretty influenced by the cultural assumption that hopping around every year or two for the beginning of your career is the best way to elevate your salary so I'm starting to look around for other options (I have 2 years of total time with this company, the first year was as an intern). In my current position I fill a lot of different roles and am responsible for the planning, design, and development, testing, and maintenance of software tools for our manufacturing production line on my own. This includes a lot of getting familiar with the industry and working with domain experts to find places to optimize their production processes. I've gotten a lot of positive feedback since I started and have rolled out two major projects that have had measurable effects on speeding up parts of our productions processes that I have metrics on so I'm expecting a pretty favorable review. This industry suffers from the ~never talk about your salary in public~ culture of the past so I have no idea what to expect regarding the timing of raises, but I'm getting paid 75k base compensation with a 9% annual bonus with potential 1-3x modifier based on total corp performance for the year which is about on average for a junior developer in my area which I think is low for the amount of responsibility they have been throwing on me and are expecting from me in the next 12 months. I'd like to see about 90-100k. I'm worried that asking for a 20-30% raise is just too loving ballsy though. What's the normal protocol for asking for more money and what kind of potential fallback should I be considering? I figured I'd feel out the performance review and wait to see if a raise was even in my manager's mind to begin with and if it wasn't then ask at the end if everything went well.
|
|
#
?
Jan 30, 2018 04:36
|
|
|
Portland Sucks posted:I'm worried that asking for a 20-30% raise is just too loving ballsy though. What's the normal protocol for asking for more money and what kind of potential fallback should I be considering? I figured I'd feel out the performance review and wait to see if a raise was even in my manager's mind to begin with and if it wasn't then ask at the end if everything went well. Working for your company for a year or two and then finding a new job. The fallback is to drink heavily, then enjoy your "Generous" $10k raise with your promotion in 5 years.
|
|
#
?
Jan 30, 2018 04:47
|
|
|
Portland Sucks posted:I'm worried that asking for a 20-30% raise is just too loving ballsy though. What's the normal protocol for asking for more money and what kind of potential fallback should I be considering? I figured I'd feel out the performance review and wait to see if a raise was even in my manager's mind to begin with and if it wasn't then ask at the end if everything went well. The best way to do this is get another offer for what you want, and ask them to match it. If they don't, leave. Either way, you get what you want. Or slowly drink yourself to death like Volmarias said.
|
|
#
?
Jan 30, 2018 18:03
|
|
|
Skandranon posted:The best way to do this is get another offer for what you want, and ask them to match it. If they don't, leave. Either way, you get what you want. Or slowly drink yourself to death like Volmarias said. Be prepared to leave anyway even if they match it, you might be out on your ear the moment they find a replacement for you.
|
|
#
?
Jan 31, 2018 13:51
|
|
|
Anyone here have any YouTrack experience? Im trying to figure out simply how to reorder a backlog in a way the shows up for other users. Googling has suggested that there are some gotchas but Im unable to avoid them all. I can drag issues around, but its only for me, not other users.
|
|
#
?
Jan 31, 2018 14:07
|
|
|
Portland Sucks posted:Obviously, being a SE I'm pretty influenced by the cultural assumption that hopping around every year or two for the beginning of your career is the best way to elevate your salary so I'm starting to look around for other options (I have 2 years of total time with this company, the first year was as an intern). You were a bet for the company as an intern. It paid off, because you're awesome, because you worked hard and learned, because of their amazing mentorship. Right now you've grown into more than the role they hired you for. If you were hit by a bus and they needed to fill your shoes tomorrow, they're hiring one logistics expert and two midlevel programmers for a total of 3x your salary and their communication overhead would still make them slower than you overall. You're absolutely worth a 30% raise right now. Management will categorically be unable to recognize this. They're pretty sure that you'll keep working there for a 3% CoL and vague unspecified words about how bright the future will be in year 4. Their "worst case" is plucking another intern and hoping/assuming they grow as well as you did. Like others have said, the best way for you to approach this is with another offer in hand that you're willing to take. At a bare minimum, don't go into the review process without writing down the sum total of your duties and trying to match that to other local jobs, sorta filling out this bus-scenario. It'll be an awful fight to get your manager on your side, then you're relying on him to go to bat during the higher levels of the review process and convincing his management of your exceptional nature. Anyway, most folks find that uphill battle with lovely results atrocious and just find a new place that'll pay them more.
|
|
#
?
Jan 31, 2018 23:21
|
|
|
Eh, I usually go into negotiations and wind up with max they had budgeted or they have to talk to the CFO to get me hired. Only with VC-backed companies do I seem to be able to name a price that makes sense. Going higher requires some level of very demonstrable, publicly validated value such as being a well known open source contributor, deep subject matter expert in a super hot area (machine learning, Big Data, etc.), conference speaker, author, employment with well known markers of perceived ability (FANGS), etc. Because your value beyond the $200k mark isn't just as an individual contributor pumping out code to production as much as empowering others to deliver their pieces, which is basically a form of technical management.Mniot posted:What does "running out of tasks" look like for you? The other alternative outcome is bad too though - extreme overwork because an unrealistic deadline gets slapped in front of you after months (or years!) of politics and now someone else's job / reputation is on the line so you need to start delivering results all of a sudden. That scenario may actually be worse than just getting laid off because you're probably itching to do some real work but can't deliver business value that future employers want to see. Being unable to put anything up on Github, having no work, and still needing to show you're "there" is really, really stressful. Felt a lot like being one of those fake Internet users in North Korea staring at unmoving screens with armed guards around if they started to show signs you're bored / not engaged.
|
|
#
?
Feb 1, 2018 04:24
|
|
|
Even a benign we dont have anything for you is alarming and makes the engineer think they are superfluous and therefore about to be fired. Its especially bad when its a new job. I would even take a large backlog of stuff to do instead of having nothing to do, cause either I work a little more (subject to proper work-life balance) or I stop getting money to live.
|
|
#
?
Feb 1, 2018 14:18
|
|
|
Pollyanna posted:Even a benign we dont have anything for you is alarming and makes the engineer think they are superfluous and therefore about to be fired. Its especially bad when its a new job. I would even take a large backlog of stuff to do instead of having nothing to do, cause either I work a little more (subject to proper work-life balance) or I stop getting money to live. From the opposite point of view, filling out a backlog and having enough work for a new hire is actually pretty hard when you're unsure of the full skillset, level of expertise, and how long it will take for that employee to ramp up.
|
|
#
?
Feb 1, 2018 14:42
|
|
|
Blinkz0rz posted:From the opposite point of view, filling out a backlog and having enough work for a new hire is actually pretty hard when you're unsure of the full skillset, level of expertise, and how long it will take for that employee to ramp up. Which is perfectly fair - Im more thinking of this in terms of how truly a company needs me. For example, at one place I interviewed with today, I dug into exactly what the company needed in terms of head count, skill set, etc. Their response was that they dont really need an engineer, though they have wants in terms of skill sets and soft skills - theyre aiming for doubling their user base and everything dependent on their next round of funding and that may pan out, but in the short term i.e. now it didnt seem like they were hurting for a new engineer or anything yet. That made me a little nervous, since there wouldnt be anything clear to point to when asking the question why did we hire her? and makes me feel more superfluous than I am comfortable with. If I get hired, I want to know that I am needed.
|
|
#
?
Feb 1, 2018 18:54
|
|
|
Pollyanna posted:Which is perfectly fair - Im more thinking of this in terms of how truly a company needs me. For example, at one place I interviewed with today, I dug into exactly what the company needed in terms of head count, skill set, etc. Their response was that they dont really need an engineer, though they have wants in terms of skill sets and soft skills - theyre aiming for doubling their user base and everything dependent on their next round of funding and that may pan out, but in the short term i.e. now it didnt seem like they were hurting for a new engineer or anything yet. That made me a little nervous, since there wouldnt be anything clear to point to when asking the question why did we hire her? and makes me feel more superfluous than I am comfortable with. If I get hired, I want to know that I am needed. You're never needed, but you can add value and that's ultimately the why did we hire her that you should be considering in my opinion. I don't think I've ever asked myself if my employer needs me because I know I'm replaceable, but I'm always asking myself how or if I'm providing value and how I can increase that. edit: To be honest you don't want to be needed. You're working under bad management if anyone is full on needed. How can you take a vacation if you're needed?
|
|
#
?
Feb 1, 2018 18:59
|
|
|
I'm looking for some opinions on the scope of commits going into code reviews. We have a lot of plugins and a common task is to make one. There are two ways I see to manage this from a code review standpoint: 1. Get the single commit that implements all requirements of the plugin, end-to-end, in one hit. Spin around on this with feedback and patches until it's set. When it's finally accepted, it's considered production-ready. The master is generally considered production-ready. The developer might make that initial single commit from a series of topic branch commits squashed together. They will also probably have to rebase the source a few times while this all is churning. 2. Get a sequence of commits for the plugin representing major "thoughts" towards fulfilling the plugin. This may still come from personal, squashed commits, but less of them. There will be more unique reviews but the reviews themselves would be shorter. When accepted, they aren't necessarily regarded as release-ready. Master is not considered production-ready. There is a mechanism for separating works-in-progress from production. Architectural work-in-progress code is "dark" in master until feature-complete. Right now we're doing #1 and it's leading to reviews taking over a week sometimes, and also sometimes resulting in architecture (not plugin) changes that are so large that the reviewers can't really make sense of them any more. I'm looking at #2 as a greener pasture that might be just as bad.
|
|
#
?
Feb 1, 2018 20:58
|
|
|
|
| # ? May 13, 2024 00:13 |
|
|
Rocko Bonaparte posted:I'm looking for some opinions on the scope of commits going into code reviews. I'm not a fan of either approach. Code review isn't the place to be ascertaining functional correctness -- that's what unit tests, integration tests, and QA/UAT testing are for. Code review is to catch obvious mistakes, style issues, horribly inefficient algorithms, etc.
|
|
#
?
Feb 1, 2018 21:13
|
|
