bkovacev

Not sure what you're using for your api framework, but you can definitely fetch only particular fields on your get requests with Django Rest Framework.

Also, you can definitely version nicely. You just have to document it well. If you're supporting different api version in you're bound to add more code, not sure what that argument is about, since I assume (could be wrong) you'd have to define a new schema and add new logic to handle the queries in the translating layer, correct?

Also, the author makes a bold title and then goes ahead and mellows it in the first few paragraphs. Stick to it or don't do it at all.

How did you switch into training?

That's actually amazing, lucky you! I'll give the new LTS version a go for sure as I still love ubuntu!

The investors always protects their own interest - remember that. They not only bet on the technology, but also on the people behind it. Depending on the agreement, the investor might not "owe" you anything. Thus, if they invested in another product in the same emerging market, they're trying to ensure greater % of success and ROI for themselves.

But, you do "owe" things to an investor - like reports, hard work etc. What you do, however, OWE to yourself is that you protect your idea/product to the fullest.

Thus, you only feed them what they need to know, thus disclose only relevant financial info. If they ask for other info be sure to be brief. Don't disclose the actual details about the tech behind it.

I assume if you know who they invested in, you know the amount and probably the terms, thus assess. More investments > higher risk > higher reward. If those investments were <250k, that's normal and I wouldn't be to worried about it.

No, not really.

I have a high-end laptop from Asus (no plastic etc) that I installed ubuntu on. It would overheat, have issues with the drivers and just simply would consume more power. It'd maybe last for an hour, while on windows same processes it would last for two and a half. No matter how many hacks I had to google for and how many hacks I tried, still nothing worked. You've wasted six hours, I've wasted a month trying to optimize my laptop to work at 50% of what it did.

I have had a Mac as well that I sold in a heartbeat, because it required an upgrade that I simply was not willing to pay for. For less than double of the amount of money it required for an upgrade I got 32GB of RAM, 512SSD and a neat i7 processor, zero plastics. Mac would also overheat and would also crash, your point? Plus the support in the region where I am located is ZERO.

No I'm definitely not going to miss the keychain as I have last pass that handles just about everything nowadays.

I also work on Python, postgres, ansible, redis (which has limited support on windows but still works). Not sure where your problem is.

So there's also the other side of the coin, plus your isolated case + opinion does not prove the "ZERO quality" statement, just like mine doesn't that's it's good.

Celery?

I'm not sure if I understood this correctly - you had to interview for another team within the company, even though you've already went through that same process once? If true, that's ridiculous.

For a senior role - "Basic"/pointless problems are those algo questions you would ask at the big 4. Rarely will you find a senior level engineer knowing the best solution to inverting a binary tree or any other text book problem you know because 9/10 times those are not used at all in any of the most common real world cases.

However, what meaningful questions will cover are advanced architectural problems, particular inner workings of a tool/framework, how to squeeze in the last few drops of optimization etc. Conversation should flow without any major breaks and the most experienced engineers will talk about edge cases of edge cases, thus continuing the conversation themselves. You can discuss different types of architectural patterns, ins and outs of each one and how it can be applied to a particular problem.

You should not waste the engineers time on textbook questions if you value yourself or the interviewee, and as the parent comment stated - the engineer should walk out if they start asking "basic" questions. Someone that worked in the industry for 10-15 years should not be bothered with them.

Big step in the right direction. I also believe this will have huge impact on the morale as well. If you offer enough courtesy to your employees you'll receive a lot more in return. Personally, I believe this can boost productivity in a different way, because if the employee is challenged with a different set of problems other than the "same ol' " during the work time, the experience can be directly applied to the possible future employer's problems.

Granted, this can have downsides too.

Being part of an offshore development team and a consultant I can tell you that clients mostly find us/me through networking and referrals. Mutual acquaintances, word of mouth and weirdly LinkedIn gave us most work.

But, as solomatov said previously, best way to do it is via a middleman. The middle man is from the offshore country and has most likely been in the US for a couple of years and has created a wide network of potential clients. These were by far our best clients. I know at least 4,5 eastern european consultancies that started this way.

If you have those same developers willing to allocate time and their resources - sure, go for it. With most eastern european countries it's important to have them dedicated to things. Your costs will be lower, your production will be higher (ymmv) and if funding is not a problem you should definitely try that out. Remember they are all "mercenaries". You will learn a lot just being in another culture. Most friendships you create there will last you a lifetime. YMMV though, as with anything.

This feels like communism. It does not matter how hard you work, you will all get paid the same. Why should someone that worked better be rewarded the same as someone who did not work so hard?

Leave the things as they were initially. Let customer decide the performance part of the pay, you just take care of the base portion.

Unless, all they really want is the 10% for themselves.

Hey, first of thank you for your hard work! Let me redefine my argument - free level of support is somewhat lacking.

To be fair - this was like year and a half ago. Two separate issues. The previous company I worked at was where the issues occurred. First issue was something related to the NDB. I do not exactly recall what happened, as it was right when I got there. I do recall people being whining about delayed replies and ended up re-deploying to another instance.

Second issue was a fee for a service we have not used (big data/query I believe)- it took a while for the support to reply(something along the lines of couple of business days - billing support btw) and after we got ahold of them we have spent a lot of time on the phone trying to figure things out and we were still charged for that month. It was not much, but we could have purchased the current silver package for that money.

After the company started selling more products we upgraded to Gold package which was excellent. That's about the time I left.

Another separate instance was when I was not allowed to create more apps (even though I deleted more than 6-7) and I had to make a request for my account to create more. That took couple of days as well.

I think I started using GAE around 2011 and since then I have only seen improvements :)

I have used GAE a lot. They have improved tremendously over the last couple of years and have also extended their services. However, as noted on in the previous comments - support sucks.

Advantages:

- Easy to set up.

- Cheap to start (somewhat like Heroku). Especially the moment you start optimizing for performance it's easy to cut down on the funds needed each month.

- Scalable. Google takes care of it.

- As someone mentioned versioning. It works as easy as changing the YAML file.

- Deployments are fast and painless.

- Amazing cloud administration with beautiful and easy UI. Unified logs.

- Ease of integration with other Google products and APIs.

Disadvantages:

- Lack of proper support.

- Documentation is sometimes lacking.

- Lock-in. Oh man does it hurt if you want to move away from GAE.

- For python for example, you can only used C based python modules.

- HTTP request 30 seconds. 10mb limit. Datastore is I believe 1mb. Blobstore 50mb.

- Gets expensive the moment apps become bigger (somewhat like Heroku).

I'd definitely wager where your app will be in a month, 3 months, six months and a year and see if GAE is a viable option. Think of API integrations as well.

Thank you. I'll be sure to mention that to him! :)

Exactly - talking with someone who is going or went through the same is invaluable as no one can understand you better than someone who shared the same struggle. It doesn't have to be an advice, but just the fact you are not the only one and not alone is extremely comforting.

Plus, the bond it creates lasts for a lifetime and it just takes your friendship to a whole new level. Usually the people you struggle with, you remember for life.

I've had a two year period where my feelings were dominated by apathy and depression. Nothing appealed to me anymore, friends, going out, video games, programming, school, work. Literally nothing. My parents, gf told me they loved me and while I said something back, I did not really feel it or mean it.

Best advice I received was from my dad - in life you have three different types of inner motivation:

* fire and anger are the initial drive - they help you start something

* professionalism and existentialism - they help keep you going

* self-fulfillment - they help you finish

One motive that is inwrought through all these motivators is "sometimes you have to be your own hero". You have to have the fire, you have to have the professionalism, you have to fulfilled. Not others. Step it up, I'm sure you have it in you!

Don't give up, your life has purpose and you are valuable :)

Where exactly are you from? Are you in Eastern Europe by any chance?

In this case I do believe it's a Virtual Assistant :)

From my personal experience what the parent comment stated is actually very true.

As someone who is actively trying to get into the JS world coming from the back-end side it is extremely hard to find best practices that do not change every other week. In the beginning of the year, tutorials were made with grunt, yarn, yeoman and the likes, then they were written to use gulp, bower and now it's webpack and what not. I can't even catch up on what the tutorials have used. To be extremely fair, every other week there seems to be a new tool I need to know and I can't even catch up on why I should learn or stop learning/using the previous. Every tutorial/documentation does something differently - there is no unique set of tools and instructions that do not change over time. I cannot find the best practices docs, because everyone has their own opinion of something and bashes the other guy for having an opinion in the first place.

I know it might be a bad analogy - but I usually compare the state of the principles of RESTful APIs to the state of principles of the front-end stack. They are design principles and you have set of instructions/best practices you should follow regardless of the language, framework etc. Thus I can make RESTful APIs in Python, Go, Ruby etc. On the other hand, Javascript is very opinionated framework. I cant seem to find the principles wrapped in a talk, book or docs. Offer me a choice, let me make it, do not make it for me. Let me make a mistake, let me learn how it does not add up to the whole picture.

Every JS documentation assumes something or fast forwards through an important part of the process - the set up. Why the heck do I need to use something, and why is it good with another tool you have in this stack. Why shouldn't I use something? Don't just copy the gulpfile or any other js file I need, explain it.

You said it is a good thing to try a new thing every month - how do you have enough time to observe it and test it properly in production or wherever? I don't see a new framework every month as a good thing, the frameworks don't mature in your environment and neither does my deep understanding of the framework. That makes for constant struggle to optimize a way. People in the JS world, at least to me seem like, hmm, this does not sound cool anymore let's change it up with this.

I hope I don't come of as a hater, I'm just speaking as a front-end newbie.

SEEKING WORK // REMOTE preferred, will relocate // Any timezone.

Full stack developer with 5 years of experience.

Keywords: Python, Django, Flask, REST, Django Rest Framework, MySQL, NoSQL, mongo, redis, javascript, jQuery, Angular, bootstrap, HTML, CSS, datastore, AWS, Heroku, EB, Google App Engine, GAE

Linkedin: https://linkedin.com/in/borkopolo

Github: https://github.com/bkovacev

I'm available for 30+ hours a week.

If there's a match, or you would like to consult/talk about a project - contact me at borkopolo+hn [at] gmail [dot] com

hello, do you mind sending one to borkopolo (at] gmail . com

Why does it have to be a special treatment?

While I know most of the people here might be against it:

* last pass - password manager

* noscript, ublock

I am, however, most of my friends are running a start-up or are safe in a corporate job. I tried my best reaching out, but without any luck. I had one potential client talk, who said he will be in touch if he gets funding approved.

This sounds and looks extremely interesting. How can I contact you?

Please let me know :) I'd love to see it and play around with those tools, they'll cut my work time tremendously. Thank you!

Sure, because excess muscle causes excess work from your body in order to keep it. However, bear in mind that for some that is a profession and not a matter of choice.

Would you mind sharing the github repo?

Extremely biased, awfully researched post. If you look at his recent stories he is on an apple hype train. Nothing against apple, but this guy has blurred and biased judgment.

No need to be sorry - we just misunderstood each other, although the wording was a bit harsh. You are right - I should have provided the context. I apologize. I'll remove the link.

edit: cannot remove the link for some reason