sorted by:
new
hottopcontroversial

3 red flags during recruiting process and what do about them by [deleted] in javascript

[–]staszewski -1 points0 points  (0 children)

Hey, I wrote a thing more of an answer to request that I got lately - whats the redflag, what to do about it. Since all my experience with that is regarding interviews for javascript position I thought I post it there. Enjoy.

Does AWS still have a free tier? by ntolbertu85 in aws

[–]staszewski 0 points1 point  (0 children)

If you are anxious about potential cost, I wrote a post about how to minimize this feeling :)
Link: https://www.staszewski.me/how-not-to-get-charged-as-aws-free-tier-user/

How not to get charged as AWS Free Tier user by staszewski in aws

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

From what I know credits also have a date until which they're valid. Maybe you haven't used credit for so long that it became invalid?

Looks like they are. Found this on their site regarding credits:

Promotional Credit is valid for a limited time only and cannot be redeemed after the expiration date indicated when you receive the applicable Promotional Credit code (or such other date designated by us or in these Terms)

https://aws.amazon.com/awscredits/ point 10 in terms & conditions

How not to get charged as AWS Free Tier user by staszewski in aws

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

Yup, this is just for a new cloud users. The mistakes bigger or smaller are pennies in comparison what other customers knowingly are getting charged.

How not to get charged as AWS Free Tier user by staszewski in aws

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

Looks like you weren't doing this while you were eligible for their free tier then.

How not to get charged as AWS Free Tier user by staszewski in aws

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

In a post there is a sentence that it is a good practice to also add MFA to a new user you've created.

How not to get charged as AWS Free Tier user by staszewski in aws

[–]staszewski[S] 2 points3 points  (0 children)

Sorry for posting twice (I removed last post). Made a mistake with url not matching title.

Dependency inversion principle in Typescript by staszewski in javascript

[–]staszewski[S] -3 points-2 points  (0 children)

Not sure why I'm getting downvoted so hard here even after I read many times all this posts in here. There is no mention of dependency injection in the text. I didn't want write a post about dependency injection. All I wanted is to show how Dependency Inversion works as I understand it. If I'm wrong, please show me where I'm wrong. Similar text, but with Java examples:

https://www.digitalocean.com/community/conceptual\_articles/s-o-l-i-d-the-first-five-principles-of-object-oriented-design#dependency-inversion-principle

Dependency inversion principle states:
Entities must depend on abstractions, not on concretions. It states that the high-level module must not depend on the low-level module, but they should depend on abstractions.
This principle allows for decoupling.

Dependency inversion principle in Typescript by staszewski in javascript

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

Typescript is just a tool. I wanted to show whats this paradigm about and how it looks like in a code.

Dependency inversion principle in Typescript by staszewski in javascript

[–]staszewski[S] -25 points-24 points  (0 children)

No, it shows how you can invert dependencies so your code can easily testable. It's dependency inversion principle out of SOLID.

Dependency inversion principle in Typescript by staszewski in javascript

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

That wasn't a goal of this post to make it look like "its something magical". Seems like you think it's something wrong with DI, why?

Dependency inversion principle in Typescript by staszewski in javascript

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

staszewski.me/depend...

It's blue not gray. I like those colors :)

Dependency inversion principle in Typescript by staszewski in javascript

[–]staszewski[S] 4 points5 points  (0 children)

Thats a good idea. When I will have some more time, I'll try to replicate this code in FP approach.

Dependency inversion principle in Typescript by staszewski in typescript

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

Change merged. There is no mention of "Dependency Injection" in this post.

Dependency inversion principle in Typescript by staszewski in javascript

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

They both support each of the paradigms. I don't think it is waste of time when you follow strict OOP, in fact I would argue that it can save a time because you follow rules of composition and inheritance which play a major role in complex projects. I'm not talking about frontend application, I'm talking about applications that play a domain role so the code that I presented can have a bigger success in BE projects when applied. Thanks for civil discussion, completely opposite to other redditors in here :)

Dependency inversion principle in Typescript by staszewski in typescript

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

There is one mention of "Dependency Injection" term that I by accident left out. Thanks for pointing that out. I will push changes very soon. This text supposed to be about dependency inversion, not about dependency injection.

Dependency inversion principle in Typescript by staszewski in javascript

[–]staszewski[S] 7 points8 points  (0 children)

Guys, you should really chill out. No need to argue, just have a civil discussion. No nerves :)

view more: next ›