i think the same, i think backend where data is more prominent is not going anywhere soon. llms produce very bad data structures.
but from good apis, good data, good interface they can generate quite nice frontends.
i guess, frontend as job is going to have a hard time.
also, writing code is not cognitive load, its always reading code. and llms just increase that. so i mostly try to avoid using them.
but i do like researching with them. context free. like googles ai mode, etc. not from my code editor cause then they get biased and suggest stupid sh8t all the time.
volume of low quality content, dsa/leetcode, etc. is so high, good people/content gets left out. networking, connections, nepotism so much high. getting job based on actual talent very rare.
MNCs which are good outside are so much sh8t here; well capitalism doesn't give a f8ck anyways.
I think you'll get downvoted to oblivion because outsiders often don't realize the ridiculousness of the whole thing.
I will try to give some context.
To give an example, the CSE undergrad from an average Indian college would've done 500 - 1000 leetcode "problems" for practice. But have little to no idea on how to survive in a UNIX shell, or to troubleshoot an actual problem. Hell, half of them haven't written more than 1000 lines of code for single purpose.
People early in their career (which is most SWEs including yours truly) follow whatever "influencers" on youtube (the local term being bhaiyya-didis), who give them rough "roadmaps" to "crack DSA" or "get high paying remote job". The result is that average CS guy spends most of his time navigating this rat race than studying computer science stuff that matters for the job.
I see similar kind of competition getting created at senior levels too, in the terms of people grinding theory and blog posts on "system design" interviews. I am not old^H^H^H senior enough to comment on it, though.
But it was not all bleak. IIRC, We were producing quite few good OSS contributions through GSoC, LFX etc... until few years ago (not considering my own among good ones). There were talented 1% or so (I known a few very talented people in personally). Nowadays these "hustler" variety people have started "How to crack GSoC" roadmaps [sic] too, and the spamming quoted above see may be related to this. This sort of insane rat race is not good for talented people. It's not good for companies either. Recruitment is basically lottery at higher levels too; I have seen people use AI to shamelessly lie on their resumes and get hired etc... Some of these problems may be present in west but India's scale makes some of these problems difficult.
this is a problem with all indian "education". I work in renewable energy and regularly chat with other Indians at IEEE conferences who are looking for work in the West.
These supposed electrical "engineers" have an IEEE "paper" to their name but regularly confuse power and energy. They have no curiosity, no interest in their work, atrocious communication skills (not language, communication) and swarm you like piranhas once word spreads.
All this combines to devalue Indian degrees and the reputation of Indian STEM talent. The genuinely good people are drowned under this avalanche and there's not much you can do to help them or to find them.
IEEE might as well be a predatory publisher. None of their journals are serious anymore.
Hell, CVPR is now the top conference/journal in the world, beating out every medical journal, Nature, etc. NeurIPS I think is also beating out every medical journal ever.
If you're not targeting a top 20 listed conference/journal in your field as ranked by google scholar (i.e shows up on the leaderboards at all), you might as well not even publish, as those papers at worse venues act as a black stain on your academic career.
These folks should instead target workshops at prestigious venues.
> These supposed electrical "engineers" have an IEEE "paper" to their name
"publication" is encouraged or in some cases "mandated" in certain institutions for course points. It's a lecherous system to game certain metrics which leads to pretend-play and not an ounce of productive work.
> there's not much you can do to help them or to find them.
In CS, If you want to find talented Indian folk, you can hang out in IRCs, hobbyist forums etc.. I have few friends who were Linux enthusiasts, compiler experts etc... who used to. Genuine interest is a pretty good initial filter.
what advantage/disadvantages does Scala/jvm have over Elixir/otp/beam?
i am learning Elixir and liking the concepts.
i am coming from kotlin/jvm and i like kotlin, apart from kotlin-coroutines.
planning to migration all threading code to virtual threads. but biggest problem is threadlocal.
I think they're pretty different, but there are some places where you can compare them:
1. Hiring and job market - the JVM is simply more employable
2. Ecosystem - in general you can expect the JVM to have library support for most things you're going to need.
3. Typing - if you like static types, you're probably going to miss that in Elixir/Erlang. They're working on a gradual type system for Elixir that looks quite pragmatic, so I'm excited to see how that works out.
The Elixir side of things has some real advantages, though. Runtimes like the JVM are slowly adding threading paradigms that start to look like how the beam works, if you squint enough. Naturally, Elixir already has that, and already has technologies that work very well with it. Virtual threads on the JVM are a smart effort that will take a long time to be complete and will always have to take backwards-compatibility into account, especially if you're in Java itself.
Phoenix is also IMO a best-in-class web framework. I don't think it's universally applicable, but if any JVM language had something like Phoenix I doubt I'd be considering Elixir nearly as strongly (due to my affection for types). So while the JVM ecosystem is broader, it's not uniformly stronger.
I also think that "domain" is much broader for JVM stuff. The web technologies there feel pretty baroque rather than empowering, but you can still do web on the JVM, and Kotlin or Scala in particular IMO serve better for systems where the bulk of the code is internal business logic. I think that even if I adopted Elixir entirely, I'd probably retain some "second language" for deeper systems.
How do you know it? Today you have to re-assess what you've learnt in the past. If you think JVM is "simply more employable" and haven't tested the waters in last 1-2 years, chances are you're just wrong.
The feeling I have: more simpler the tech is (and JVM/Ruby/other CRUD), the highest salary cuts you're getting. And you're actually less employable.
It is that counter-intuitive, because it's one person with a coding agent vs a team in the past.
This is patronizing. I'm a professional and am constantly hiring and being hired. The JVM has far more jobs and engineers willing to do those jobs, _and_ in terms of your own employment, a better salary market, and this is not only self-evident, but reinforced by even a cursory investigation into the trends. In fact, your claim is so outrageous (that I'm wrong and that somehow Elixir has more to offer on either side of the hiring bar) that I think the onus is on you to somehow prove it.
- "expand my social circle"
same here, try to make real world connection not just technical connections but with people i can hang out with, friday night parties, trips, etc.
apart from work i don't have any connections. opportunities are lacking and idk how to increase my chance.
if anyone in Bengaluru, India having meetups invite me, duckydude20 at gmail.com
i find him everywhere theres is mention of loki. trying so hard to push down loki. sure loki have issues but i don't feel this is a good approach to promote your product.
I'm trying to push Loki developers to fix these issues to make Loki users happy. What's the point to hide these issues? The won't disappear on their own over time.
I'm very glad to know about VictoriaLogs issues, so they could be addressed quicker. If you hit such issues, then please file them at https://github.com/VictoriaMetrics/VictoriaMetrics/issues or publish an article highlighting these issues.
I highlight Loki problems, so potential users are aware of them when choosing log management system. It is Loki's developers business to decide what to do next - to fix these problems or continue hiding them, so users discover them the hard way.
for me, it was a hard time grasping CIRD and concept of host address tbh. playing with ciso packet tracer and rip, ospf... still not understanding ipv6 and all those huge infrastructures. like ipv4 to ipv6. carrier grade nat. BGP, peering...
idk, i am new to goland but same thing, tls issue. my tests were very flaky. sometimes they were failing sometimes they weren't. i initially thought it was wsl and goland issue. but after it happened 2-3 times. i ran with goroutines test with -count 50 but it didn't work in goland. then i issued in terminal. which i got to see yup my tests are actually flaky.
i know this is not the best way. but i added a timeout of 10sec. also while asserting i am polling to know if i got a connection.
i understand and i can make it way better. but for now it's good enough.
more importantly, it's better not scatter these kind of codes everywhere.
also making things explicit is better always. like now server.Start is Blocking. and in my tests i am spawning a goroutine, rather than it doing implicitly.
another thing, testing dependencies. i am going to test concurrent handler. and it's not dependent on tls or tcp. i can just use a fake and test the concurrency.
i like this design. scattering these throughout will make every other test integration tests. increasing time to execute and that is bad.
btw, it would have been better if go lang runs tests in parallel.
https://github.com/sku0x20/no-libc/tree/main