Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
quintes
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
30 ms
·
241.
▲
by
quintes
9y ago
This
242.
▲
by
quintes
9y ago
Perhaps rephrase, not sure the question is clear
243.
▲
by
quintes
9y ago
I said team city. Then realized you said Oss Take a look anyway
244.
▲
by
quintes
9y ago
Yep this. Or heroku
245.
▲
by
quintes
9y ago
Is it the same projects/ code for all clients? If so do they get the same built product? 1 backlog. Different code for different clients? Many backlogs. Projects share code base maybe? Then you need Prioritization, planning and if you
246.
▲
Ask HN: Team password manager
1 points
by
quintes
9y ago
|
2 comments
247.
▲
by
quintes
10y ago
Unless you're starting with zero.. Skills on the team? Current stack? If nothing then I do this: Git and stash. An agile approach, features and user stories. An agile board. Vsts or rallydev Yes to continuous integration, deployment
248.
▲
by
quintes
10y ago
I tell people as a joke that back when I did device / integration work we didn't call it IOT we called it TCP. Really. Discrete values over wonderware sql or modems transmitting level readings. If course it wasn't internet
249.
▲
by
quintes
10y ago
Find a client or two who can become your subject matter experts in exchange for early access / beta releases. They'll validate it and know your market. so similar clients will meet the fit
250.
▲
by
quintes
10y ago
Picking the language and then the specifics of what you want to improve knowledge of is next. specific e.g in Python use OOP to build a x using (flask or bottle and JavaScript flavor of the month here). Phase things as well, don't try
251.
▲
by
quintes
10y ago
I'd consider myself mature. What are you wanting to get out of a community? Sometimes my stories may interest or bore younger devs but man I like listening to them, sometimes they show me something new or Shiny, and sometimes I may eve
252.
▲
by
quintes
10y ago
Master, dev, feature and release. Mostly always in fact. An admin merges a release back into Master and back through to dev after a milestone build, demo or production release. Keep the same Workflow with other teams in your organisation if
253.
▲
by
quintes
10y ago
Take your b12 vitamins too. Do not eat poorly, take the time to make food lists and get what you need so you don't end up eating less nutritious food. Try tofu. initially eating at bbq may be tough but your friends and family will supp
254.
▲
by
quintes
10y ago
I've proposed new product ideas on both data and intuition. Sometimes it worked, sometimes I had to right it off to experience. This is relevant to both new product development and just new features. Sometimes a new product is a good i
255.
▲
by
quintes
10y ago
I've prepared packages and distributable for many enterprises and it's always CD as in continuous delivery not deployment, except on dev servers. A delivery may be a zip archive run via bash or powershell, or more of traditional
256.
▲
by
quintes
10y ago
I've even seen it used to describe the support team who really just fix the bugs and get the changes into prod by some means... Not my Definition but something I've seen.
257.
▲
by
quintes
11y ago
fancy... But perhaps a proper system is what is needed, I.e. An existing invoicing system. Why do we always have to build everything when something better exists?
258.
▲
by
quintes
11y ago
I didn't understand the comment from person 2.. I would say keep learning about it and playing but you know as do I you don't have to move to it now just cuz it's new.
259.
▲
by
quintes
11y ago
check in when it makes sense. In a feature branch? whenever you like as long as it's building often. In a dev branch directly? often enough so change gets into test regularly but not so often that your small change sets break the build
260.
▲
by
quintes
11y ago
This is how I make money sometimes... resource hire or consult gigs and help out with new tech, automation, delivery/process or do/fix things the development team can't do. So I would like to continue being paid, and the comp
261.
▲
by
quintes
11y ago
The comments about js build process with these new tools is something I share.. when you see the dependencies being pulled down and things are getting included my first reaction is... What am I shipping. It's good to raise that questio
262.
▲
by
quintes
11y ago
codenvy.com was neat but I ended up going back to net beans and Visual studio
263.
▲
by
quintes
11y ago
I've tried at that price point. They won't pay that but will want you to do more for less. Small business has proved to me that even a simple cms is not something they think their business needs. They're happy to trial and ha
264.
▲
by
quintes
11y ago
Things will only get more difficult. pick the stack and move on.
265.
▲
by
quintes
11y ago
Cordova
266.
▲
by
quintes
11y ago
unit test first so you know if you've broken it. Then lots of test input variations best taken from production sources. Refactor thereafter and test after each iteration of changes. It's not a rewrite, so don't lose the plot
267.
▲
by
quintes
11y ago
Having worked on a large python code base as well I can tell you that sometimes it's hard. Look at the types, determine if they're instance of and try build small test runs around existing code before you modify it. python tools f
268.
▲
by
quintes
11y ago
Bitbucket or just host it on your remote and ssh in
269.
▲
by
quintes
13y ago
Works on my machine
270.
▲
New tld's and revenue generated
2 points
by
quintes
14y ago
|
0 comments
More ›