Jump to content
Search In
  • More options...
Find results that contain...
Find results in...


  • Content Count

  • Joined

  • Last visited


This user doesn't have any awards

About FakezZ

  • Title
    *Insert unfunny and unoriginal member title here*
  • Birthday Jun 22, 1998

Contact Methods

  • Steam
  • Origin
  • Twitter

Profile Information

  • Location
  • Gender
  • Interests
    Programming, music, cryptocurrencies, artificial intelligence, chess, economics, beer
  • Occupation
    Software Engineer and University Student (I know happens to the best of families)


  • Operating System

Recent Profile Visitors

2,306 profile views
  1. So I recently I read a bit about GraphQL and I proposed it at my company. We decided to try it on a medium-sized project we had. The impressions were mixed. I, working on the backend, found it very easy to work with it. Adding new fields to types was really easy and if I wanted to add a new computed field to a model, I had to edit just one file and write a single resolver and it was accessible everywhere this existed without having to make sure I include it in every endpoint. On the other hand, the frontend guys were not really that positive What I saw is that they had a bit of a hard time wr
  2. I will definitely give it another try, but my other points still stand about the language. I have given it a try many many times, unfortunately.
  3. Well, I am not really turning it down easily. In fact, I started programming with C++ since I was like 13 or 14 (even have some later projects up on github as well) and even though I don't use it for anything professionally, I still follow all the updates and spin up some test projects when I have time. However, I find a lot of things are handled very very poorly. My biggest problem is that it is so hard to use third party libraries. It is something that should be simple, but it ends up being a pain in the ass, leading you to either use huge libs like boost, or reinvent the wheel and hack arou
  4. Yeah, but you could argue that even C++ is running on top of assembly, but I doubt anyone thinks it's a good idea nowadays
  5. Oh based on how you approach learning, you are definitely on the right track. The thing you said about languages not being a problem is spot on actually, basic programming skills and good engineering will get you far in any language or field. I don't really think you should learn front-end unless you are also interested in being a full stack dev (good full stacks are rare and usually quite in demand). I would start with the basic protocols of communication in the web (how TCP works, then the HTTP protocol) and then start with API design. How REST APIs work, how they are designed,
  6. I wouldn't be so sure. Modern programming is different in terms of concepts too, though. And I doubt C/C++ being the way they are can keep being used for much longer. Oh I am sure the module system will be a failure. With every C++ standard I just keep getting disappointed. I guess you can't really teach an old dog new tricks
  7. Yeah I hope so. I mean I like the way the keyboard feels and types, but the fact that it is unreliable is a big issue. The travel and feedback are fine for me, but I just can't stand not being sure if a key press registers or not.
  8. Yeah I know, but I have been dealing with this keyboard for a year now, a few more months are not that bad
  9. Okay that is nice. However I am still not going to shell out 3k for the same keyboard design that has failed me and everyone I know that has the laptop. The rumors say that the 16 inch model will have scissor switches again and if so it's going to be a buy from me. Otherwise, I might just stick with the machine I have.
  10. They did? Because I read that Apple extended the free keyboard replacements for the 2019 models too and I've been very hesitant.
  11. Well, actually there will be a module system in the C++20 standard (possibly, they promised it in C++17 but it never happened), so it is definitely not impossible and does not have anything to do with low level. Rust has a really nice module system, is also low level and the performance is on par with C/C++. The thing is that all the proposals for the C++ modules are imo not that great and kinda hard to use. The problem with the standard library is that they just keep on adding stuff, sometimes "replacing" older ones without deprecating them and they never break backwards compatibility, w
  12. From my experience (working professionally as a Backend developer for a year), you should not learn Java frameworks. Actually, it all depends on what you want. Currently, the jobs for Java and C# programmers etc are mainly to maintain old code. I doubt many new projects are made with them (maybe with java since it has evolved quite nicely, but has a bad rep). The hot things right now are NodeJS (kinda biased here since I use node all the time), Rust if you want to get your hands dirty, Go if you want to be somewhere in the middle in terms of abstractions, Python if you like the language (perso
  13. I just want the new keyboard to be honest... I am a developer and I've had many keys get stuck or register twice, leading me to almost breaking my desk because the build failed for some reason or I pushed the wrong image. The worst of it is, in Greece, they need 2 working days to replace the keyboard and I cannot afford to be without a computer for 2 full days. Once the new MacBook is out with the new keyboard I'll be the first to preorder.
  14. Oh yeah they are backed by central banks who can print as much as they please. Thankfully we can trust them and the wars by governments to keep the value of our currency stable huh?
  15. Actually there are a whole bunch of scams running with fiat digital currency. Many many many more than crypto, just because it is a much bigger market.