If you were born in June and you're competent and trustworthy and hold CEO and CFO designations in a good Business and a good Industry Structure - you can stay ahead of the curve and create wealth.

Keywords :: June And Competent Trustworthy CEO CFO Business Industry Structure

If u are looking to enter a scrip just before the breakout
what would u look for?
How would u identify scrips just before breakout?

Here are a few pointers
Carefully understand the them and use at ur own discretion
(All comments r compiled from a question i posed)

1/23

Price is testing the same resistance repeatedly since long.
But now in recent times it's forming multiple candles near the same resistance with low volume.
Observe it and see for opposite move.
As soon as u get a positive candle, get in to it.

2/23

1. Volume buildup (vol > when resistance point created) along with, increase in OI, increase in delivery % on HTF
2. On LTF, price stalling around breakout area for at least 1-2hr.
3. No major events.

3/23

Stock reaching breakout LVL with HL-HH
Contraction of price and volume near it especially near 20 days ma.
If there is any breach of the latest HL it should be followed by a bullish candle with good volume.
Left side of the chart has a rally with a very steep slope of ma.

4/23

Number of wide range green bars with high volumes.
If stock is at its ATH then it adds more conviction bcz there wont b supply after that point

Consolidation below the resistance, volume of the candles & strong bullish candle closing at near highs just below the resistance

5/23

A thread on HN about bad code in legacy projects both makes me think how little we've learned as a discipline over the years and, honestly, how little credit we give ourselves for some pretty major

Fun going down this list and thinking: "Hmm, plausible at a well-run modern software shop", "Hmm, possible, but requires implausible tradeoffs", "Literally disallowed by languages", and "If you were to attempt doing that our test suite wouldn't let you merge."

I think we as an industry celebrate (not quite the right word) failure too much and don't celebrate success nearly enough. There is no DailyWTF for competent execution, word of which generally stays pretty local to the source while incompetence passes into legend.

Alrighty let me try to thread the needle on being the change I want to see in the world while not giving away anything that will get me in trouble:

Ruby has wonderful developer ergonomics. Typed languages are easier for machines to guarantee the correctness of. We built a type checker for Ruby (and I believe it is slated for OSS release sometime).

c.f.

Most software founders, particularly in B2B, need to get radically better at sales. @Steli , who is the best person for explaining the scrappy stages in the beginning and then building out a team with scripts and processes, wrote a guide to:

For technical founders it is irrationally, obscenely hard to reverse years of programming (ba dum bum) that sales is a value-destroying activity. Sales is CLEARLY a value-creating activity, contingent on you have a value-creating product.

The world will not drop what they are doing to adopt your work. This is particularly true in B2B, where simply building a better mousetrap won't overcome the activation energy required to get people with additional non-mice problems to prioritize changing mousetraps today.

This is very non-obvious for founders because founders are not often people who *want* to be sold to. We often come from a background where trying out tools is a bit of a fun hobby. We like looking at all the options, making charts, and ripping out partially complete tests.

"This week I unsuccessfully trialed four software options for automating that thing that has been killing us. Our actual production process remains the same as last week. Don't worry; this was a great use of time." is not a thing you want to write in a progress report to manager.