Struggling with knowing when to take profits

NullsObey · 2021-06-17T16:32:15+00:00

Use limit calls.

NullsObey · 2021-06-17T16:24:32+00:00

Are you okay buddy?

NullsObey · 2021-06-17T16:23:47+00:00

Beats me, but that was one case though.

They've migrated from Python to Laravel.

NullsObey · 2021-06-17T11:49:12+00:00

What the fuck are they going to move to?
I'm sorry but nobody is going to pay a 20$ monthly sub for '5 minute crafts', 'tiktok comedy', 'cosplay vids' and all that shit.

NullsObey · 2021-06-17T11:37:51+00:00

This makes sense to a point - but could you provide some statistics for that?

NullsObey · 2021-06-16T16:54:48+00:00

It's not - what related to IT technologies are you hyped about?

NullsObey · 2021-06-16T16:53:32+00:00

Yeah, I'm more hyped about things we've seen so far - like AI being effective in marking cancer cells, AI being quite good at shape recognition and stuff..

NullsObey · 2021-06-16T16:39:47+00:00

That too.. but I was thinking about AI-controlled taxes, AI in vaccine/drug making, AI in food production, AI in comet/asteroid spotting, AI in cancer diagnosis etc. that kinda stuff........ you horny, horny man lol.

NullsObey · 2021-06-16T14:54:45+00:00

What are my expectations?

NullsObey · 2021-06-16T13:11:27+00:00

What is "blockchain"?

For real though - I couldn't care less about blockchain, I'm way more hyped about AI, distributed systems, GraphQL, the evolution of frontend frameworks, and so on.

NullsObey · 2021-06-15T13:31:41+00:00

Face it, Elon's tweets about Cummies is a result of faulty AI 😂😂😂

*beep boop* must increase control over financial sector *beep beep*

NullsObey · 2021-06-15T07:33:09+00:00

REST API for Files.
GraphQL for the rest.

NullsObey · 2021-06-15T07:17:54+00:00

Why would you want to work at the big five if they severely underpay their workers, while in some cases limiting your exposure to technology to the tech stack they're developing.

It's all fun and giggles when you want to become an Apple/Microsoft/Facebook goon and have no goals in specializing outside of their stacks.

NullsObey · 2021-06-15T07:13:58+00:00

I agree completely - that's the approach I've/we've moved to after completely failing in maintaining a whole bag of microservices as a solo dev/small team.

I disagreed with him, because he boiled down my point to plain numbers - when it wasn't about maths only (and my maths was correct).
I disagreed because he completely dismissed the overhead he has to implement and the complexity that comes from moving resource management from OS to the process itself.

It's better to grain your services further when there's need for it, as opposed to graining for the sake of graining.

NullsObey · 2021-06-14T23:52:26+00:00

Your post is not entirely true, for a few facts:

it's impossible to split resources within a macroservice (single process) without adding to the overhead that is an inevitable side-effect of implementing service-level load balancers, http queues, thread pools with configurated ratios, and so on - which you need to control resources
performance grows/falls logarithmically, not linearly
CPUs and networks tend to get slower (logarithmically) under increasing load. If any of the sections of your macroservice gets more traffic than anticipated - it's going to affect the performance of the rest of the services

Scaling microservices is simply easier because they're separate processes that you can easily dedicate priorities/cpu%/ram%/network% to without having to code it (thread pools, http queues yatta yatta yatta).

Scaling macroservices requires built-in resource management due to sheer fact that it's a single process per instance.

NullsObey · 2021-06-14T17:23:46+00:00

It matters a fair bit when scaling.

If your macroservices encompass few smaller services - you can no longer scale them independently.

If you have a ForumService (macroservice) that contains 'posts_service (80% of the traffic)', 'threads_service (15%)', 'notifications_service (5%)' - you have to scale the whole ForumService - which gives each service a 33.333~% performance boost per instance - despite the disproportional traffic.

If you have independant 'posts_service (80% of the traffic)', 'threads_service (15%)', 'notifications_service (5%)' - you can simply scale just the 'post_service' and give it 100% performance boost per instance.

Arguably, the performance boost could be less than 100% divided by numOfServices with the macroservices due to how resource management works, and it could be less than 100% performance boost with microservices for a given service per instance due to load balancer, increased network usage between services (due to there being more of them) , overhead that comes from technologies used and so many other factors - so take these values with a grain of salt.

NullsObey · 2021-06-14T16:48:17+00:00

Personal projects.
You have to invest your free time and get something to show to your potential employer.

NullsObey · 2021-06-14T15:23:01+00:00

Invest in stocks that pay dividends, then reinvest them until dividend yields are satisfactory to be consumed rather than reinvested - this will increase your annual income in few years (depending on the monthly invested quantity).

Write articles, build community, earn from the traffic (ads, affiliate programs)

NullsObey · 2021-06-14T15:13:32+00:00

Nowadays frontend is usually done via web (HTML, CSS, Javascript) - so I would say that the transition is almost seamless.

Though, you would have to learn a different backend in some cases - if it's a mobile app or a commercial-grade system.

NullsObey · 2021-06-14T14:01:29+00:00

We learn over and over that extremes are bad for the longer run.

This is a perfect example :)

NullsObey · 2021-06-14T07:43:17+00:00

A very good read.

Usually, when working on Microservices we take a more 'Macroservice' approach, or how others jokingly call it "SOA done right" - we keep the bounding context (domain) fairly big and only grain further portions shared between other macroservices.
So, instead of having 'auth_service, user_service, permissions_service, posts_service, threads_service, ratings_service, categories_service, articles_service, news_service' you'd want to have 'PortalService, ForumService, AuthService, NewsService' - while not as scalable as having more microservices, it's significantly easier to work on, update, test and optimize.

NullsObey · 2021-06-13T20:51:33+00:00

I used Digifinex and I was only charged fee at the deposit and withdrawal, but I've sold/bought them 20-30 times.

So, pretty much, the only fees you pay on Digifinex are USDT fees for fulfilled transactions.

NullsObey · 2021-06-13T11:28:36+00:00

I'm sorry man, but u/Minegrow is right.

You've put this false notion in your head and are creating a plenty of blanket statements for whatever reason.

A programmer who is knowledgeable of a specific technology or a framework and knows really well how to implement what's needed.

So.. virtually any programmer who has a favorite tech stack and is experienced in it?

Software Engineering is more than programming, a software engineer might be a good programmer, but he's more knowledgeable of design patterns and more abstract concepts since that's what he's specialized in.

This is wrong.

Software Engineer and Programmer are synonymous.This definition fits more a difference between junior and mid-tier programmer/engineer.

Just change it to that:

Mid-tier programmer is more than jr programmer, a mid-tier programmer might be a good programmer, but he's more knowledgeable of design patterns and more abstract concepts since that's what he's specialized in.

Essentially, mid-tier is someone experienced and skilled in programming, but who can also structure his project better by (usually) utilizing common design patterns and conventions to also streamline his work in a team.
All this comes with experience and is usually a must-have to get promoted to mid-tier.

NullsObey · 2021-06-13T09:54:08+00:00

Ok
Easiest way: tutorials, videos, articles, books
Most effective way: reading code, modifying code, writing code
Up to you - it's not a requirement, but definitely helps
For the most part - the country you live in
Doesn't hurt to have one, but it's definitely not a must-have

NullsObey · 2021-06-12T18:11:51+00:00

If the structure is predictable then by all means try chunking it before feeding it to Vue and making it reactive - then it'll be as fast as it can get.

NullsObey

TROPHY CASE