|
Pretty sure you guys are putting way more thought into this than leper khan ever did
|
# ? Apr 18, 2017 14:19 |
|
|
# ? Apr 25, 2024 12:08 |
|
Pollyanna posted:Pretty sure you guys are putting way more thought into this than leper khan ever did
|
# ? Apr 18, 2017 18:59 |
|
ultrafilter posted:For now. Keep a deadline, though; you don't want them to just keep promising that something better will happen eventually for the next year. You're right and honestly I'm probably doing myself more harm than good. It's just day after day of completely baffling management incompetence. I'm now redoing something I spent 7 days on because nobody mentioned a small requirement to me lol
|
# ? Apr 18, 2017 19:16 |
|
Just received word that our entire platform/AWS operations team quit. Rats fleeing sinking ship, etc. This is fun.
|
# ? Apr 18, 2017 20:01 |
|
Pollyanna posted:Just received word that our entire platform/AWS operations team quit. Rats fleeing sinking ship, etc. This is fun. ... And then you handed your own notice after them, right?
|
# ? Apr 18, 2017 20:49 |
|
HardDiskD posted:... And then you handed your own notice after them, right? No, that's when you go for the promos soon and title change. Use that new title to leverage a better job. Then give notice.
|
# ? Apr 18, 2017 20:58 |
|
Haven't put in my notice yet, but I'm polishing up the ol' resume and been scoping out new opps for a while now. The schadenfreude from this is glorious.
|
# ? Apr 18, 2017 21:04 |
|
Is there a good place to look for remote contract opportunities? A lot of freelancer places seem geared toward designers or people in Belarus who can work for $10/hr.
|
# ? Apr 18, 2017 21:44 |
|
fantastic in plastic posted:Is there a good place to look for remote contract opportunities? A lot of freelancer places seem geared toward designers or people in Belarus who can work for $10/hr. StackOverflow careers has actual filters for both remote and contract, also there's a remote work aggregator site goremote.io that doesn't have an actual filter that I can see but if you just search for "contract" in the descriptions that seems to work alright.
|
# ? Apr 18, 2017 22:05 |
|
Thanks. Somehow I totally blanked on StackOverflow careers.
|
# ? Apr 18, 2017 23:51 |
|
remoteok.io, remotebase.io, weworkremotely, StackOverflow and Indeed are what I check daily Indeed sucks a lot, but you do find jobs there that aren't posted anywhere else. https://news.ycombinator.com/item?id=13271393 has a lot of others, ymmv
|
# ? Apr 19, 2017 02:17 |
|
Iverron posted:remoteok.io, remotebase.io, weworkremotely, StackOverflow and Indeed are what I check daily The real trick is to get these contracts at $X/hour then sub-contract them via those other sites for $X/hour/10 and WIN.
|
# ? Apr 19, 2017 03:41 |
|
Dogcow posted:StackOverflow careers has actual filters for both remote and contract Also Authentic Jobs.
|
# ? Apr 19, 2017 04:54 |
|
They've got some work to do on their mobile site:
|
# ? Apr 19, 2017 05:43 |
|
Idk that's a pretty sweet tumbler you should take it
|
# ? Apr 19, 2017 06:03 |
|
leper khan posted:On the plus side, anyone at less than 6.2 figgies should have an easy way to change that while they're trying to hire literally everyone. Do you still have to move to Seattle?
|
# ? Apr 19, 2017 12:38 |
|
Pollyanna posted:Just received word that our entire platform/AWS operations team quit. Rats fleeing sinking ship, etc. This is fun. Didn't you want to get out of web dev? Seems like you could dabble in this and see if you like it.
|
# ? Apr 19, 2017 12:40 |
|
smackfu posted:Do you still have to move to Seattle? Nah, they have offices all over the place. Several of my friends recently started at amzn robots which is in MA. They claim reports of people crying at their desks are mildly exaggerated.
|
# ? Apr 19, 2017 12:50 |
|
Sign posted:Didn't you want to get out of web dev? Seems like you could dabble in this and see if you like it. From what I've heard of what they do, it's still web dev in the sense that they're wrestling with network technologies and AWS, plus they were getting pulled onto all sorts of other teams to gently caress their Rails/Node/whatever problems, and that's what apparently got them fed up enough to quit. Maybe at a different company, I'd be curious about platform stuff, but not here.
|
# ? Apr 19, 2017 15:15 |
|
Pollyanna posted:From what I've heard of what they do, it's still web dev in the sense that they're wrestling with network technologies and AWS, plus they were getting pulled onto all sorts of other teams to gently caress their Rails/Node/whatever problems, and that's what apparently got them fed up enough to quit. Maybe at a different company, I'd be curious about platform stuff, but not here. "Web dev" is traditionally thought of as mostly comprising the code that outputs the stuff you see in the browser. Communicating with AWS or other software services is not really part of that domain. I mean, what if your database is stored on AWS? Is your backend therefore web dev?
|
# ? Apr 19, 2017 15:20 |
|
TooMuchAbstraction posted:"Web dev" is traditionally thought of as mostly comprising the code that outputs the stuff you see in the browser. Communicating with AWS or other software services is not really part of that domain. I mean, what if your database is stored on AWS? Is your backend therefore web dev? Really? I consider web dev as anything that plays a role in transferring data across some sort of long-distance protocol, or is part of a project where that is a main component. Maintaining a REST API is web dev, as is writing the front-end that consumes it and bringing up the pipelines and servers needed to build and deploy it, but the code that doesn't fetch data from an API in a mobile app is not considered web dev to me, and interacting with the database the API consumes is technically not wev dev in and of itself. Of all the things that play a role in web dev, back-end stuff like APIs and databases are the least objectionable to me. Maybe my definitions are all out of wack, which is totally possible. I've just done a lot of Rails and Node work recently and I see people doing cool poo poo like systems, embedded, writing good libraries, and mobile and I want in. I've had a difficult experience with platform (AWS, CICD stuff, etc.), but maybe "platform" means something different everywhere. It'd be good to clear up these misconceptions sooner rather than later...
|
# ? Apr 19, 2017 15:30 |
|
Pollyanna posted:Really? I consider web dev as anything that plays a role in transferring data across some sort of long-distance protocol, or is part of a project where that is a main component. Maintaining a REST API is web dev, as is writing the front-end that consumes it and bringing up the pipelines and servers needed to build and deploy it, but the code that doesn't fetch data from an API in a mobile app is not considered web dev to me, and interacting with the database the API consumes is technically not wev dev in and of itself. Of all the things that play a role in web dev, back-end stuff like APIs and databases are the least objectionable to me. Telco isn't webdev and is explicitly sending data across long distance protocol. See also real time networked multiplayer games.
|
# ? Apr 19, 2017 15:38 |
|
Remember the phrase "World Wide Web"? Y'know, webpages? That's web dev. Networking in general is a much bigger topic that web dev touches on briefly.
|
# ? Apr 19, 2017 15:43 |
|
Network programming seems interesting AF but I'm not sure how to go in that direction. I've worked on some real-time systems but I'd like to go even ~*~ lower ~*~ but its hard to find projects to work on myself in that domain.
|
# ? Apr 19, 2017 15:46 |
|
Pollyanna posted:maybe "platform" means something different everywhere. "platform," even in the every-word-means-three-things world of software engineering, just means "a base on which things are built." People commonly refer to embedded platforms, mobile platforms, content management platforms, and so on.
|
# ? Apr 19, 2017 16:02 |
|
Good Will Hrunting posted:Network programming seems interesting AF but I'm not sure how to go in that direction. I've worked on some real-time systems but I'd like to go even ~*~ lower ~*~ but its hard to find projects to work on myself in that domain. Writing multiplayer games is a fun way to get into it. It's less difficult than a lot of people make out if you have a little background in communication systems. Could also do a chat server or sensor network or the like. If you want a hobby project I've had on my list for a while (and will never get around to), you could try to take the Gameboy link cable data and packet switch it over the tubes. Then play Tetris or whatever else people do with Gameboy link cables.
|
# ? Apr 19, 2017 16:06 |
|
leper khan posted:If you want a hobby project I've had on my list for a while (and will never get around to), you could try to take the Gameboy link cable data and packet switch it over the tubes. Then play Tetris or whatever else people do with Gameboy link cables. One of the Awesome Games Done Quick streams had a section where they ran a Super Game Boy (gameboy communicating with a SNES so you could use the SNES controller and view the game on a TV), played Pokemon, jaibroke the game to run arbitrary code, jailbroke the Super Gameboy "sandbox", then replaced the SNES controller with a modified network connection that streamed Twitch chat data into a janky chat display that they'd coded in their now-thoroughly-mauled game code.
|
# ? Apr 19, 2017 16:10 |
|
When I think of webdev I usually think of Html, Css, Javascript with some UX/UI knowledge. the V in MVC. Someone that could split a pdf into an html template. I also reffer to that as front-end dev. When I think API, Databse, data transfer, number crunching I usually think of back-end. Someone that can reason about architecture and back-end component and how they interact. I usually don't consider that web dev, even if you do end up using HTTP protocol and Xml and json and stuff like that.
|
# ? Apr 19, 2017 16:47 |
|
Pollyanna posted:Really? I consider web dev as anything that plays a role in transferring data across some sort of long-distance protocol, or is part of a project where that is a main component. Maintaining a REST API is web dev, as is writing the front-end that consumes it and bringing up the pipelines and servers needed to build and deploy it The API part is arguable if you're delivering JSON to a browser which is running JS and effectively amounts to a fat app executed client side, but that's mainly because you can't really build it any other way but iterating on the stuff providing the data while iterating on the user-facing stuff. It sounds like your work sucks but I advise not overcorrecting to the point that the sort of work you're doing now is poisoned in the future with a potentially better work situation.
|
# ? Apr 19, 2017 17:28 |
|
AskYourself posted:When I think of webdev I usually think of Html, Css, Javascript with some UX/UI knowledge. the V in MVC. Someone that could split a pdf into an html template. I also reffer to that as front-end dev. Yep. If you are outputting data into a WebView/WebKit derivative you are doing webdev. If you are posting JSON RPC requests to a HTTPS endpoint as a serialization piece of a 3d resource management game, you are not doing webdev.
|
# ? Apr 19, 2017 17:33 |
|
Hughlander posted:If you are posting JSON RPC requests to a HTTPS endpoint as a serialization piece of a 3d resource management game, you are not doing webdev. "Services work"
|
# ? Apr 19, 2017 20:47 |
|
Hair splitting ITT
|
# ? Apr 19, 2017 21:43 |
|
Any good D3 tutorial recommendations? Going to need it for a new position I just started.
|
# ? Apr 19, 2017 23:25 |
|
dantheman650 posted:Any good D3 tutorial recommendations? Going to need it for a new position I just started. The D3 maintainer has set up example scripts for just about every possible type of graph at https://bl.ocks.org/. I fully recommend copying one that looks like your use case and then modifying it, every time. It's a very feature rich library, and unless your entire job was to create interactive graphs, it's going to be faster/easier than starting from scratch. If it is going to be your entire job, I would still recommend copying an example chart and modifying it, because it will give you more insight into what everything does than a tutorial. - Make sure you know what version you're using and what the example is using. There was a massive overhaul between 3 and 4 that caused complete incompatibilities. - If you are using it infrequently, comment like crazy. I'm not a big code commenter, but I always leave a trail of breadcrumbs on my D3 charts so that when I inevitably get feedback to change the colors or whatever I can find exactly what I need. At first I didn't think I'd needed them, since I wrote the dang chart, but even days later it was difficult to tell where to put things.
|
# ? Apr 20, 2017 03:35 |
|
Pollyanna posted:Really? I consider web dev as anything that plays a role in transferring data across some sort of long-distance protocol, or is part of a project where that is a main component. Maintaining a REST API is web dev, as is writing the front-end that consumes it and bringing up the pipelines and servers needed to build and deploy it, but the code that doesn't fetch data from an API in a mobile app is not considered web dev to me, and interacting with the database the API consumes is technically not wev dev in and of itself. Of all the things that play a role in web dev, back-end stuff like APIs and databases are the least objectionable to me. I personally don't view Web Dev the same way. Actually, here's how I've always viewed the "Full Stack". 1) Web Dev / Front End means anything in the browser that renders or sends data, html, javascript, css, etc. You're dealing with npm, front end build tools. 2) Back End is anything that is server side. Creating the end point and accepting data in Java, Python, Ruby, etc. It also deals with APIs / SDKs (such as AWS) that might not deal with the DB. 3) DB is pretty much a DBA without being an actual DBA. Can write some really efficient SQL queries. Can model pretty well. In my experience, most devs (not all) are efficient in one or two of these. Usually in combinations of 1 and 2 or 2 and 3. If you can do 90% of 1, 2 and 3 I'd think you were Full Stack. I think most of the time it just takes exposure. In my current company this is the case and I'm trying to improve it. We've started to pair program to get everyone up to speed on all three. It's been pretty successful. I think if we can get devs to be 90% of the way there in their weakest abilities that's a big win. It's awesome when the younger developer who sits next to me asks, "Hey, I need this 'data', can you help me set this up?" and I can just walk her through all she needs to do from the DB query through the REST Api to even the front end if need be.
|
# ? Apr 20, 2017 04:37 |
|
dantheman650 posted:Any good D3 tutorial recommendations? Going to need it for a new position I just started. Previous recommendations are good. My current role leans on D3 pretty heavily and I didn't have much experience with it before hand. There's a lot of information out there as far as medium articles and tutorials are concerned. I recommend reading Jim Vallandingham's posts. Specifically, Abusing the force was a useful overview of the force module (useful for network visualizations and "bubble" abstractions). There are also Over 1000 d3 js examples and demos, though there's a big of repetition here. Good for inspiration though. Implementing D3 effectively requires UX chops that enable you to display data in a compelling way while avoiding antipatterns, but recommendations for that are probably outside of what you were seeking out?
|
# ? Apr 20, 2017 07:12 |
|
Sinten posted:Specifically, Abusing the force was a useful overview of the force module (useful for network visualizations and "bubble" abstractions). I just see a blank page.
|
# ? Apr 21, 2017 04:13 |
|
geeves posted:I just see a blank page. Arrow right with keyboard.
|
# ? Apr 21, 2017 06:21 |
|
I think this is more of a vent than actual advice asking. I'm contracting for a company that largely does Rails stuff. I largely do Rails stuff. I am currently: 1. 100% remote 2. The only developer on a team. For context the other teams are a) 3 guys doing dev VM and Jenkins stuff, b) all the other developers in the company working on a Rails monolith. 3. The only person of any discipline assigned to that team. 4. Working with a tech neither I nor anyone else in the company is familiar with (Kafka) 5. Working with a new-ish library neither I nor anyone else in the company is familiar with (Kafka Streams) 6. Writing, packaging, and deploying a language neither I nor anyone else in the company is familiar with (Java) 7. Writing puppet and defining infrastructure on some NIH IaaS that's so new it goes down at 55 minutes past every hour to clear a memory leak Apart from being a recipe for intense isolation it's also incredibly inefficient. They know this isn't my area of expertise and I've told them we could get way more done in other ways but they seem to be happy with me spending two days wrestling with Maven. I can do it because I've dealt with new tech and new languages enough to be able to pick things up, but it seems like such a waste of my time and their money.
|
# ? Apr 21, 2017 09:50 |
|
|
# ? Apr 25, 2024 12:08 |
|
Arachnamus posted:Apart from being a recipe for intense isolation it's also incredibly inefficient. They know this isn't my area of expertise and I've told them we could get way more done in other ways but they seem to be happy with me spending two days wrestling with Maven. I dunno, sounds like assigning someone who can pick things up is exactly the kind of person they want. So long as you communicate concerns clearly and flag risks, take it as some paid on-the-job training. Kafka is a good tech to pick up, and even though I've spent most of my career as an iOS dev knowing Maven and good Java patterns/practices has benefited me. With that said, doing it solo can be pretty stressful. Maybe see if you can lobby to hire a coworker? But yeah if you're getting frustrated then maybe you should recalibrate your expectations for yourself, then figure out their expectations of you, then figure out what you're okay with.
|
# ? Apr 21, 2017 10:17 |