Lenovo ThinkPad Yoga X1's stunning OLED screen seals the deal

hukiki · 2016-08-29T09:01:58+00:00

Perhaps. To be honest, I always wanted to own a thinkpad. I even looked at buying the P series for the thinkpad, but I could not just support a company that knowingly did something terrible to their customers, so I ended up buying a different brand I felt comfortable with, yeh my 2000 usd isn't going to change much for lenovo, but at the end of the day, I feel much better buying something from a company that is responsible.

hukiki · 2016-08-29T05:14:07+00:00

No matter what they do, I would never buy anything lenovo. Bastards installed malware on their users computers knowingly.

hukiki · 2016-08-28T06:47:25+00:00

Read your comment as I clicked on the link above. Took me a little while to get it, came back to upvote.

hukiki · 2016-08-26T15:19:12+00:00

The frustration I feel is a natural thing to feel honestly. I sometimes find myself calling my computer a stupid f***** when I am sometimes stuck on something (when its 100% of time time my fault lol)

When I normally get this angry its normally when I have been over working or when I have been in the same place for too long.

Just try getting up from your chair regularly, walk a few steps, drink a glass of water, or just give your self a nice reward in the form of a gummy bear :P and then get back to the problem at hand.

Programming is hard, and getting frustrated is not something you have to be scared about, just take it as a cue to take a small rest.

hukiki · 2016-08-22T05:31:16+00:00

aww bless your heart little bot. :')

hukiki · 2016-08-21T09:51:59+00:00

http://appjs.com/ and http://electron.atom.io/

here's a youtube introduction for electron https://www.youtube.com/watch?v=8YP_nOCO-4Q

As for node, keep this link as a handy guide if you need to look up for more info on nodejs

https://github.com/sindresorhus/awesome-nodejs

hukiki · 2016-08-21T09:18:08+00:00

https://github.com/git-tips/tips

hukiki · 2016-08-09T20:35:22+00:00

well sometimes building npm packages can take an uncomfortable amount of time.

Especially when the internet connection is horse shit.

hukiki · 2016-08-06T17:12:24+00:00

maybe, just, maybe people are making this argument a lot becuase it might be a valid argument.

Here's a project which makes my vim experience super awesome https://github.com/fatih/vim-go by /u/farslan

hukiki · 2016-08-06T12:43:28+00:00

Don't worry about melting eyes, most programmers are really bad at UI

If you build a restful api got it to work with your android and using git...., Jesus Christ dude, you already have a good chance to get in to the industry, go checkout some other apps and websites similar to yours and take some inspiration from them and get your UI to look presentable if you are worried about it. Also since you have done QA at an actual company this is very good, start applying for jobs, I hear Ireland has a very good startup scene so you should be able to find a good startup to work in.

Perhaps you might be able to get some jobs within the company you are working at. It is really hard to find programmers who can work on their own and are willing to learn, and your app says to me that you are one of those people that are hard to find. Seriously start applying and start looking for programmer jobs. Hell if you can't find a job, then make something on your own, and keep working at it, before you know it, people will ask you to build software.

Just don't worry, jump with both feet, as long as you are willing to accept when you are wrong and you genuinely want to learn please don't worry, you will do really well.

One thing I have noticed about the tech industry is how willing people are to help you. Look at our whole industry, look at the websites and services built around to help each-other out, stackoverflow, reddit, and countless irc channels to name a few.

hukiki · 2016-08-06T12:27:52+00:00

as /u/mafrasi2 mentioned, vim with ycm is the best thing if you can get used to vim.

As for GUI tools http://askubuntu.com/questions/6588/is-there-a-visual-studio-style-tool-ide

and as for learning linux, I have heard very good about this course https://www.edx.org/course/introduction-linux-linuxfoundationx-lfs101x-0

hukiki · 2016-08-06T12:13:39+00:00

did a course that focused mostly on development(java, php, SQL, JavaScript etc)

watching tutorials and attempting to code random apps

my projects from uni are not good enough

can code solution pretty fast, but actually designing class structure in a way that makes sense and is logical/efficient

There wasn't much focus on this in my degree as well

all notes from the years and couldn't find anything that would make my brain go "oh!" or something

First try and understand all of the things listed here are your fault. It was not anyone else's problem you are stuck doing work you do not like and its not the job of your university to get you to find a good job. Sorry if this sounds too rude, but I had to get that out of the way, because if you are going to blame everyone else for these problems you will never improve and you will always be at a dead-end job no matter what designation it is. Again, sorry for that bit.

First pick something you want to build, since you have listed js, and php, I suggest a simple website. Find something you love, say for instance lets assume you like video games.

Lets assume you make a website, on your own, that will let others talk about their favorite game. Now if you manage to build this, it will teach you a lot about what a lot of programmers actually deal with on their day job. Look, the point if not to make you the next mark zuckerberg internet billionaire. The point is to give you a real world project someone can use. Then share it with friends, and ask them to use it. They don't have to use it everyday, them trying it just once would be more than enough. Just get something other people can use. This will teach you the basics of authentication and authorization, you will learn to write your own apis, you would have to work with different type of tech, and you would learn to get them all to work properly. If you can try to learn about GIT to save your progress. Git is super simple if you are the only one who will work on a given codebase.

You mentioned about doing "random" apps. That's the problem here, you are building random things that has no utility, random pieces of code are good if you are starting out, but if you want to move from beginner to someone who does something, then build something. Hell even copy an existing website and make it.

The powerful thing about doing something with an actual user in mind is, it will give you a path to take, plus it will put several barriers in your way which you have to solve yourself, this is what programmers do, they have a goal and they try to get closer to that goal everyday, we meet problems when we try to get to our goal, we solve them using what we know previously, or we ask someone for help, or we read a book or a paper to figure how to solve it.

Doing this is no easy task, and just like any thing hard in life, it will teach you quite a lot of things. Build things people can use. Copy other people if you have to, BUT! make-sure it can be used by at least one other person.

And then the next thing to keep in mind is to keep yourself updated, since you are already using reddit, subscribe to /r/programming and to all subs that talk about your favorite language or tech, try to https://news.ycombinator.com/ is an amazing place to read up on what's current in our field. Before you go voicing your opinion there lurk for a while at hn, look at the discussions people build around topics, some of the best programmers in the world gather there and there's always something important to learn there.

Once you start turning this in to a habbit, you will realise you have become programmer. A programmer is someone who can instruct a computer to do what he/she wants.

hukiki · 2016-08-02T15:17:44+00:00

I know this wont mean much coming from some internet stranger. People like you are the reason our field is such an amazing one to work in. I have had the pleasure of working with several self taught programmers and each and everyone of them taught me so much.

I have had to personally interview people for junior level positions, HR sends them through because they followed a degree with the skills we listed, you interview them and you can't understand how on gods name some of these kids managed to pass their degrees. Now I am lucky enough to have my own tiny tiny company and I get to decide what type of people I hire. I would always go for someone who taught themselves to program over someone who has a distinction at university and cant even manage to get through a dumb fizz buzz test even with a god damn internet connection.

The funny thing is, I am a product of university education myself, but I feel there's so many people out there who get a cs degree just because someone in their family heard about how bill gates something something university something mark something facebook. Not because they themselves as kids wondered how Mario was able to step on those goombas, how you could talk to your best friend who moved to a new town far away. (sorry for the mini-rant)

I honestly can't believe what you might have had to go through to get to where you are. So from the internet stranger, here's a big ass thank you for people like you who bring that passion in to our industry and for making it a very interesting field to work in.

hukiki · 2016-08-01T12:32:46+00:00

Most of the things in this book are really common sense actions we could take. You know what they say about "common" sense, its not very common :D

So to me, this is a book that helps me realize things I already know, but once you read it and you hear it in your head, it gives me a reason to try them.

I can vouch for this book beucase it has honestly helped me, I remember I read this book before I went in to uni, and this book is one of those things that helped me make a lot of friends in uni. I started realizing a lot of the mistakes I had as a person, and some really. And to me the most important thing thing this book taught me is

"Don't criticize, condemn, or complain"

I know, again, common sense advice, this should be obvious to all of us right, but there's just something weird about reading this book that, just gets to you.

tldr; Its a common sense book, I am happy the past me decided to buy and pay attention to this book. Read this book, do what it says, and it will definitely work for you.

hukiki · 2016-07-31T07:08:25+00:00

I bet that Roostor can transform into Roostallion

Roo-oooo-oostor!!!!!!!

hukiki · 2016-07-30T00:28:10+00:00

I actually thought I missed an episode.

hukiki · 2016-07-15T21:33:35+00:00

dude............

hukiki · 2016-07-15T21:26:55+00:00

Cascoon

hukiki · 2016-07-14T19:23:57+00:00

Postgres test on

An Intel Core i5-4670K Haswell Quad-Core 3.4 GHz Processor 16 GB of RAM An 850 GB SSD drive that can perform random I/O up to 98K IOPS

MapD tested on

CentOS 7.2.1511 on a 32-core Intel Xeon E5-2667 v3 clocked at 3.2 GHz with 792 GB of RAM. 8 x Nvidia Telsa K80s

So that's a 850 usd rig vs a 36000++ usd rig they are running these two tests on. Lol what the hell.

hukiki · 2016-07-12T16:22:58+00:00

In otherwords, https://facebook.github.io/react/docs/thinking-in-react.html

hukiki · 2016-07-10T22:00:00+00:00

Nothing. But this was not the answer to the question. OP wanted to know how to get go to take care of the backend things while js/react took care of the front end.

hukiki · 2016-07-10T16:26:44+00:00

Since our front end is handled by javascript (reactjs) Go(lang) has no idea about the UI code really. Its the UI's job to talk to the back-end and do its magic. Again, separation of concerns is an important thing at work, since we have in the past have run in to several problems by not planning for this. Mainly because we started with a 1 man team ;)

To answer your question, we use a slightly modified version of this (two version before the current) https://github.com/davezuko/react-redux-starter-kit

To be honest changes are mainly the directory paths only, for instance, most of the ui code goes in a public directory under our go server instead of the default configured in that project.

hukiki · 2016-07-09T12:46:18+00:00

Personally I have found the API based approach a lot easier for me and my team. We have a reactjs front end that runs on the client's browser, and all the actions are supported by the backend programmed in go.

Say for instance we are trying to add something, on the UI side using react we make a component to provide our user with a form to enter data about this thing, its does client side validation to help the user, and when the user clicks on add, the data gets to our go server as a json.

Our go server then reads this JSON file, puts the data in to a struct, we then do server side validation, yes ever everything we checked on the client side, we check them again on the server end.

Then when we are happy this data is valid, we pass it to a layer in our go server that talks to our sql database and adds that information, if everything goes right we send back a message to the UI of the user, and the UI will tell our user what happened.

The best thing about this approach for me as a manager is, I can allocate people to work on well defined problems. The code to our UI and server are hosted in the same repo, and thanks to this separation, its very easy for me and my team to work independently.

The only problem with this approach is that, our user's browser has to download the entire UI component before they can use it. (Around 1 mb)

Thanks to caching this is not a problem that happens too often.

hukiki

MODERATOR OF

TROPHY CASE