On another note each section comes with quite a lengthy follow up material, which I found absolutely amazing to use as a starting point as well.
Absolutely love it!
110 karma · joined October 3, 2016
On another note each section comes with quite a lengthy follow up material, which I found absolutely amazing to use as a starting point as well.
Absolutely love it!
Location: Netherlands
Remote: Yes, preferably including regular face to face meetings. However I have to work in a company incorporated in the Netherlands.
Willing to relocate: No
Technologies: Mainly experienced with Javascript, React / React Native, NodeJS, C# / .NET Core. However tech stack is an easy thing to adapt to.
CV: request via email
Email: ${username} @ gmail.com
I'm a passionate software engineer that loves this craft and focuses on being more of a generalist. Knowing how to learn is a core skill I value and teaching that to the others is something I would be more than happy to do.
Ideally looking for a company / project with a reason to exist and a good roadmap to make sure that plan happens. If your tech stack is not what I am used to; I consider that a plus (as I would love to expand my horizons as well).Reach out and we can do a virtual coffee meeting. :)
Location: Netherlands
Remote: Yes, preferably including regular face to face meetings
Willing to relocate: No, but happy to regularly come over for a while
Technologies: Mainly experienced with Javascript, React / React Native, NodeJS, C# / .NET Core. However tech stack is an easy thing to adapt to.
CV: request via email
Email: ${username} @ gmail.com
I'm a passionate software engineer that loves this craft and focuses on being more of a generalist. Knowing how to learn is a core skill I value and teaching that to the others is something I would be more than happy to do.Ideally looking for a company / project with a reason to exist and a good roadmap to make sure that plan happens. If your tech stack is not what I am used to; I consider that a plus (as I would love to expand my horizons as well).
Reach out and we can do a virtual coffee meeting. :)
REST: Any time there is a new "view"; you need to go to your server and write a new endpoint.
GraphQL: You can stitch data together however you want; as long as that data is defined.
So for example if I need name of someone and the url of their children; querying it alone is enough with GraphQL whereas with REST either I need to fetch multiple times or write a new endpoint that serves both together.
GraphQL does not have the same level of complexity as Docker; nor is it as obscure. With the libraries like apollo; especially if you have a "component driven" approach; being able to craft components as truly self-contained modules is quite freeing.
Could you do this with REST? Probably. However with GraphQL managing the complexity of it is easier. This type of an argument could also be made for SOAP; since you could probably implement something like this there too. With GraphQL somebody already did that for me though; so I can just use it. I don't have to worry about creating multiple endpoints for my use cases; I only need to worry about specific entities and how to fetch them. I no longer need to worry about whether or not I am batching my queries etc because it is managed for me.
This allows me to have (to the greatest extent) plug-and-play components that I can just chuck into places.
Seems like the issue is right here.
I have changed where I live. I didn't have that many people in my life regardless - but it doesn't take much to see how isolated I've become, so any kind of _socialising_ is helpful in my quest to not go insane.
I’ve just written a very short, hopefully good explanation for merkle trees. More of a layman’s explanation type of a text but would love to get feedback. If it does not meet the requirements (I read them and didn’t see any issues, however to err is human) please let me know and will delete it.
Thanks for your time and have a nice day!
However, I think it is way too simple to be useful. People who are happy and relatively less stressed are way more productive on average. (Yerkes - Dodson Law applies here)
Remote: Partly remote is usually preferred. A bit skeptical about full remote unless the team is able to stay connected well.
Willing to relocate: No, however I'd need continued visa sponsorship. Currently here as a highly skilled migrant.
Technologies: Mainly React Native (have been using for 4 years now) and mobile oriented full stack with lots of Javascript work. Apart from that NodeJS, C#, C++. Have spent a portion of my career in freelance projects (read: got projects and delivered them) as such have been able to work with different technologies. I am really interested in learning, as such definitely open to any polyglot environments.
Résumé/CV: Have 4 years of experience, always React Native, at times different technologies to support it (need backend, put NodeJS. Need to add a plugin to a music program, put C++, image processing? get me some CUDA etc) Have been in Netherlands for a year now, before it was in Turkey. Computer Science graduate.
Email: htkibar at gmail
System works, apparently.
1. This is less of a "AI" issue, more of a UI/UX for specialized tools issue. Dreamweaver comes to mind especially; the moment you are trying to get something that can be flexible and accommodate different needs it is mostly about learning the tools. Often, the result is that learning the tool itself is almost harder than learning to code.
2. Any code that you generate via AI will most probably be crap. A huge part of coding is making it understandable and easy to touch later on; how can you do this without AI that has a proper understanding of the worlds (probably on the level of a AGI).
If the place has such a problem, they can mitigate it ofc. For example, you can limit the chargers for example (or arrange tables in a fashion that would limit it). Then the amount of squatters would be limited.
Also, as another commenter said, you can just turn the wifi down (or limit the time). You can even charge for the wifi.
1. Version numbers are not that much of an indication to stability. RN is much more battle-tested. 2. Udacity and AirBnB both have been using React Native in a "use the bad parts" fashion. (Specifically, they have been using it with an existing app instead of from scratch). It is not really fair to React Native to be honest. However one thing from Udacity is quite fair, RN is much worse on Android in comparison to iOS.
I think giving it a try and having something new in your toolset is a nice idea. However, I doubt Flutter will be "RN is dead long live the new RN".
Finally, I really don't trust Google not to axe this project too on a spite. However that might be more personal so keep it out of the equation.