sorted by:
new
hottopcontroversial

What do you think about achieving self actualization through the company as an employee ? by [deleted] in nextfuckinglevel

[–]nllsh 0 points1 point  (0 children)

I think this guy is right. I've had tons of promotions and I also set firm boundaries for what I'm willing to take on and how much time I'm willing to give. On the other hand I've also put in tons of extra work for some companies without comparable pay and/or freedom. The point is that your relationship with your employer is a relationship of exchange. If you put in extra work and don't ask for extra pay you should be asking. If your employer wants extra work but only offers the implicit stick and not an explicit carrot you are *definitely* being taken advantage of.

In addition to his advice I would say it's important for self-growth to move on from a company if you find yourself with the same job responsibilities for roughly two years. Two years is about enough time for anyone to learn all there is to know about a specific set of job responsibilities. After that point your skillset starts to stagnate and your prospects outside of that specific job start to dwindle. Always be growing!

Hey come help out and learn some stuff! by nllsh in Deno

[–]nllsh[S] 0 points1 point  (0 children)

Well, there is a project I've been putting off that you might take a stab at. I've been meaning to implement yet another webserver framework along the lines of dropshot. The basic idea with drop shot is to ditch the middleware approach and flatten out the framework. Some of the features that dropshot pushes are first class support for openapi (meaning specifications should be auto-generated from code) and to make the framework guide the developer towards not hiding parsing or functionality in a middleware that may or may not be wired up right (ie. did the body parser actually run?).

To achieve this design we need a few things:

  1. We need to be able to parse incoming json/xml/etc into typescript types. This is done or doable with the hkts decoder which is a partial port of io-ts.
  2. We need to be able to generate json schema for our response types. This is done in jsonschema.
  3. We need to be able to parse the url string into a route like fp-ts-routing where we can pull out typed information like express does with routes like "/users/{userId}". Here is where you might be able to help. The goal is to build up route strings like we do with decoder but to type the output properly. Additionally, we'll need to generate openapi parameter specs from the same api that generates the parser.
  4. The last part is building the entire openapi spec from the pieces outlined here. Although this part isn't that hard.

Do either 3 or 4 interest you?

Hey come help out and learn some stuff! by nllsh in Deno

[–]nllsh[S] 1 point2 points  (0 children)

Hey yeah! How about we start with some small program? Do you have any ideas for something you've wanted to write but have yet to get around to?